aboutsummaryrefslogtreecommitdiffstats
path: root/tests/testimplicitconversions.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Added the "<custom-type>" tag, and better requirements for function signatures.sb-0.10.10Marcelo Lira2012-03-091-23/+19
| | | | | | | | | | | | | | | Trying to find a non-qualified (without scope information) class, found in a function signature or return type, was a bad idea for it makes the parsing awfully slow when dealing with huge libraries. If the user writes a type in short form in a function signature (e.g. "SomeClass", instead of "Namespace::SomeClass"), APIExtractor will exit with a message indicating the error and the possible candidates for the type. The "<custom-type>" tag is for types of the target language ("PyObject" in Python, for instance) and will be handled by the generator. Reviewed by Hugo Parente <hugo.lima@openbossa.org> Reviewed by Paulo Alcantara <pcacjr@gmail.com>
* Tests if added constructor with custom type creates an implicit converter.Marcelo Lira2012-03-091-1/+9
|
* External conversion operators are now part of a class' implicit conversions.Marcelo Lira2010-02-261-0/+32
| | | | | | | AbstractMetaClass::implicitConversions() returns externally declared conversion operators in addition to its own implicit constructors. The implicit conversion tests where extended with the new case.
* Fix AbstractMetaFunction::implicitConversions.Hugo Lima2010-02-081-0/+122
- Public ctors added by the user with 1 value-type parameter are always added to the implicity conversion list. - If the ctor visibility of an function was modified from public to private, the function isn't added to the result. Reviewed by Renato Araújo <renato.filho@openbossa.org>