From: Arno P. <ar...@pu...> - 2011-03-23 21:29:28
|
I am absolutely OK with the patch. I personally have favored making use of strongly typed API when creating the Java Cocoa API and that is what you do for NSSelector. HOWEVER: your patch does not make the necessary changes to the C backend. If you commit the patch as-is, it will break the C backend. Its OK to continue to do work on the Objective-C backend while we are still in transition, but I would expect that whatever change is done to the Objective-C backend is also done with the C backend. Arno On 3/23/2011 9:17 AM, Panayotis Katsaloulis wrote: > After some previous discussions, I have decided to have a better view at the > NSObject.performSelector method. > > Here is a proposal, to fix it before I start making drastic changes: > > http://xmlvm-reviews.appspot.com/111006 > > This patch is far from being ready for submission, it is more to have a look at the API first. > The two important files are: > http://xmlvm-reviews.appspot.com/111006/diff/1/src/xmlvm2objc/compat-lib/java/org/xmlvm/iphone/NSObject.java > and > http://xmlvm-reviews.appspot.com/111006/patch/1/3 > > What do you think? > > > PS: I was a bit influenced by this object: > http://www.spice-of-life.net/wodock/api/com/webobjects/foundation/NSSelector.html > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _______________________________________________ > Xmlvm-developers mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-developers |