Bug 419 – ApiExtractor requires full qualified name in some places

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 419 - ApiExtractor requires full qualified name in some places

Summary:

ApiExtractor requires full qualified name in some places

Status:	CLOSED WONTFIX

Product:	PySide
Classification:	Unclassified
Component:	ApiExtractor
Version:	HEAD
Platform:	All All

Importance:	P4 enhancement
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-10-15 21:32 EEST by Lauro Moura
Modified:	2011-06-22 20:25 EEST (History)
CC List:	8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Lauro Moura 2010-10-15 21:32:51 EEST

Currently it is requiring the full qualified name in some places, like function
arguments in function modification argument and probably in
add-function/return-type too.

It should accept "non-qualified" (AKA nested) names there too, to keep the
consistency with the nested ones.

Comment 1 Matti Airas 2010-11-23 05:47:24 EET

Is this a duplicate of bug 417?

Comment 2 Hugo Parente Lima 2010-11-23 09:05:43 EET

No, isn't.

This bug is about the need to still using full qualified name on some tag
attributes on nested tags.

Comment 3 Hugo Parente Lima 2010-11-23 09:11:12 EET

Oops, I read more carefuly the bug 417 and it's really a sub bug of this bug...
I mean, this is a generic version of bug 417 and much more harder to implement
I would say.

Anyway I prefer do not mark this bug as duplicated and fix the bug 417, because
imo the bug 417 has more worth to the bindings developer than this one.

Comment 4 Matti Airas 2010-11-23 09:13:48 EET

If it's something potentially useful, I wouldn't make it P5. Bumping to P4.

Comment 5 Hugo Parente Lima 2011-05-30 17:11:57 EEST

As discussed with Lauro and others despite of the usefulness of this feature
isn't worth implement it due to the amount of work required, besides it doesn't
add any new possibilities to ApiExtractor, just a syntax sugar. Marking as
WONTFIX.

Comment 6 renato filho 2011-06-22 20:25:07 EEST

release 1.0.4