| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It works for primitive, container and value types. Object types doesn't
have conversion rules because they can not have implicit conversions,
and the regular conversion is always the same (get C++ object held on
Python wrapper, and finding/creating a Python wrapper to a C++ pointer).
Unit tests were added.
Documentation was updated.
Reviewed by Luciano Wolf <luciano.wolf@openbossa.org>
Reviewed by Renato Araújo <renato.filho@openbossa.org>
|
| | |
|
| |
|
|
|
|
|
| |
And an unit test was added.
Reviewed by Lauro Moura <lauro.neto@openbossa.org>
Reviewed by Luciano Wolf <luciano.wolf@openbossa.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
user.
The entries that could be dropped are:
* Object and Value types
* Global functions
* Namespaces
* Enums
The entry name must be fully qualified with scope items separated by a
dot (.) and beginning with the module/package name.
Example: to drop the class "Bar" inside the namespace "Foo" from the
"Pkg" package specify it with: "Pkg.Foo.Bar".
TODO: The parser will later complain that dropped entries found on the
headers are not found in the type system. That's obviously incorrect,
but to fix it all the type entries should store the name of the package
from where the came. And that's a needed improvement!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of:
<enum-type name="Foo::Bar"/>
<value-type name="Foo"/>
the nested version could be used:
<value-type name="Foo">
<enum-type name="Bar"/>
</value-type>
The old usage is still allowed.
|
| |
|
