2009/9/21 Logan Barnett <logus...@gmail.com>:
> This will prevent Monkeybars apps from upgrading without some big changes.
> Since a Monkeybars app gets its own standalone JRuby, I'm not too worried
> about changes that aren't backwards compatible. I'm sure this will be similar
> for any app that must integrate heavily with Java.
>
> Is there a way we can have a smart proxy vs. a dumb proxy? With the talks
> I've done people seem mostly interested in how trivial it is to bind to Java
> in JRuby. While having to do to_ruby or something similar on any Java proxy
> isn't a ton of work, it's no longer as simple as just dropping in the Java
> object and running with it.
>
> Everything else seems great!
Yes, as Tom mentioned, this is the most visible and contentious aspect
of the proposal. It is obviously more standard to not automatically
coerce return values, since there's no analog for that in existing
Ruby dispatch logic, and since in some cases you can't even *get*
certain Java objects into Ruby right now. But it does potentially
break cases that expected numbers to come back as Fixnums, strings to
come back as String, and so on.
I have a prototype of this dispatch logic working, and the coerce_to?
and to_java pair really feels "right", but I have not gotten to cases
where there's coercible return values.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
