[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-swt-dev] Re: Mac port: Status Update
|
Well I wouldn't go *that* far <grin>, apparently Sun's working hard to speed it up significantly in J2SE 1.4 ....
Anyhow, what I'm finding in my bits & pieces of experiments with Cocoa -> JNI is that while we have to use NSSelector to do event handling, the underlying ObjC version is probably fast enough for general use.
Cheers
Stu
On Wednesday, December 12, 2001, at 09:29 AM, Mike_Wilson@xxxxxxx wrote:
As an old Smalltalker (and someone who worked on Method.invoke(...) for the VA/ME class library), I'm always amazed at how much work is done by reflect. In Smaltalk, you could trust that "perform:" would be only about 2x slower than just sending the message. In Java, Method.invoke(...) can be 20x slower or worse. There other issues with using reflect, like making it very difficult for library optimizers to detect which methods can be removed or optimized.
Basically, reflect is one of those things to be avoided. Heck, it's nearly as bad as finalization. ;-)
McQ.
