[Qt-jambi-interest] Jambi with Groovy

[Gunnar Sletta]

> Thanks for the reply.
> 
> May I humbly suggest that setProperty be changed to setQProperty as this 
> would seem to be consistent with other naming in Qt.

Hi Toddy,

Changing setProperty -> setQProperty would make the API very 
inconsistent, and is not an option. Its called setLayout, rather than 
setQLayout(), for instance, as the first one is easier to read.

The real problem here is that Groovy makes the assumption that 
overriding a method named setProperty() / getProperty() is ok. Given 
that these names are very generic and likely to be used in any 
framework, I can't understand that Groovy thinks this is an ok thing to 
do. Other scripting API's normally prefix their "special" functions with 
some "magic" to avoid nameclashes like this, like for instance "__py_" 
or "js".

When I dug in their bug database, I found this task:

http://jira.codehaus.org/browse/GROOVY-2326

Its the exact same scenario, although with the get function. Its marked 
as fixed, but is still broken, so I filed a bugreport to reopen the task.

So, long story short. We consider this to be a bug in Groovy, and will 
not compromise our API to support it.

best regards,
Gunnar