[hafqa] [hafqa] [Bug 814] INVALID_CHAR defined twice

[From: bugzilla-daemon at maemo.org]

https://maemo.org/bugzilla/show_bug.cgi?id=814





------- Additional Comments From daniel.kitta at gmail.com  2006-10-23 16:15 -------
Arguments in favor of always namespacing enumeration constants:

1) Bugs like that just cannot occur.

2) API inconsistencies due to ad-hoc conflict resolution are avoided. E.g.
HildonDateEditorErrorType defines NO_ERROR whereas HildonTimeEditorErrorType
uses NO_TIME_ERROR, obviously to avoid a conflict with the former.

3) Automated tools for generating reference documentation or wrapper code can
properly do their job.  For instance, right now each non-namespaced enumeration
must be wrapped by handed in hildon-fmmm and hildon-widgetsmm since the code
generator only works with predictable naming conventions.

I'd volunteer to perform a global search/replace cycle in the Maemo repository,
as this would in effect reduce my workload down the chain.


-- 
Configure bugmail: https://maemo.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.