lp:~pyside/pyside/apiextractor

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

414. By Teemu Kaukoranta <email address hidden> on 2013-05-23

Replaced Nokia copyrights in header

Replaced old Nokia copyrights with Digia copyrights.
Removed "All rights reserved" strings without leading copyrights were
removed (for example, 'Copyright SomeCompany, all rights reserved
remain untouched).

Did NOT touch contact details, will change them later.
Excluded folders that have '3rdparty' in path.

Used command:
find . -path '*/3rdparty/*' -prune -o
-exec grep -ilI -E '.*Copyright.*Nokia.*' {} \; |
tee >(xargs sed -i -r '1,10 s/([ \t#*]*)(.*Copyright.*Nokia.*)/
\1Copyright \(C\) 2013 Digia Plc and\/or its subsidiary\(-ies\)\./I')
>(xargs sed -i -r '1,10 s/(^[ \t#*]*)(all rights reserved.*)/\1/I')

This excludes binary files and retains whitespace and #* characters in
the beginning of the edited lines.

Change-Id: I9b960d54cfe46a85be86b524e95e3ee875933fb6
Reviewed-by: Sergio Ahumada <email address hidden>
Reviewed-by: Janne Anttila <email address hidden>

413. By Paulo Cezar A Junior on 2012-03-09

Fix BUG #1086 - "generatorrunner segfault processing #include..."

Boost headers typically include the character '#' at the beginning of
any line and just do nothing elese with that unnamed directive. So as
that's not actually an error, rather that's just a just-do-nothing
directive we'll ignore this situtation. There's still a problem when
using #include directives and passing macros as arguments rather than a
path to the header file. Instead of asserting this issue we'll print a
warning message about this issue.

One can also include a path between brackets (for e.g., when defining a
macro or so) so that we cannot simply ignore that. So we need to handle
this kind of stuff as well.

See http://bugs.pyside.org/show_bug.cgi?id=1086.

Signed-off-by: Paulo Alcantara <email address hidden>
Reviewed-by: Hugo Parente Lima <email address hidden>
Reviewed-by: Marcelo Lira <email address hidden>

412. By Marcelo Lira on 2012-03-09

Version bump to 0.10.11.

411. By Marcelo Lira on 2012-03-09

Added the "<custom-type>" tag, and better requirements for function signatures.

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 <email address hidden>
Reviewed by Paulo Alcantara <email address hidden>

410. By Marcelo Lira on 2012-03-09

Function signatures including return types are reported as invalid.

This fixes bug #1101: "Report invalid function signatures in typesystem"
http://bugs.pyside.org/show_bug.cgi?id=1101

409. By Marcelo Lira on 2012-03-09

Fixed type resolution for types inside scopes, but their names omit this information.

408. By Marcelo Lira on 2012-03-09

Fixed typo on warning message.

407. By Marcelo Lira on 2012-03-09

AbstractMetaTypes for object types used as values must have the Value usage pattern.

406. By Jerzy Kozera on 2012-03-09

Fixed compilation error for gcc versions < 4

Reviewed by Luciano Wolf <email address hidden>
Reviewed by Marcelo Lira <email address hidden>

405. By Marcelo Lira on 2012-03-09

Fixed insert-template tag when used inside a module level inject-code tag.

Also added unit tests.

Reviewed by Hugo Parente <email address hidden>
Reviewed by Luciano Wolf <email address hidden>