Just noticed a thing, thanks to John Lam. Our JumpExceptions derive from
RuntimeException. That means that code that will catch(Exception) will
stop flow control, if it happens at the wrong place. To get around this,
I believe we should consider going to have JumpExceptions based on
java.lang.E
Thomas E Enebo wrote:
>
> Could people who respond say what they are using in production and
> when they moved from Java 1.4 if using something newer ?
>
We have built our app on 1.5 and all of our customers are running 1.5 if not
1.6.
+1 to moving up, and keep up the good work.
--
View th
Again, why not use Retroweaver (http://retroweaver.sourceforge.net/)
to backport a 1.4.2 compliant JRuby as well while coding in Java 1.5?
Still, I can't tell how well retroweaver works, I never used it.
BTW I'm also in favor of java 1.5. in the company I'm working I see
more and more java CMS th
If I may add my 2 cents, us enterprise types sometimes also like the
flexibility that choice offers: sometimes only one requirement of an
important tool is enough to upgrade a whole set of boxes.
And believe it or not, lack of 1.5 support by another JVM language we
used in a project (NetRex
Unless the fix for serialization that I sent as a diff get rolled in,
serializing any Ruby object will attempt to serialize the entire
runtime, including things that can't be serialized. Like threads,
dynamic methods, etc.
On Jul 24, 2007, at 12:20 PM, Kyle Maxwell (JIRA) wrote:
DRb hangs
Ola Bini wrote:
I am against such a move. I would love to have some of the features in
Java 5, but the fact of it is that most "enterprises" are still on 1.4.
I believe JRuby is very important especially in the areas where
conservative values reign, and moving to Java 5 will totally destroy
th
DRb hangs when transferring Ruby objects created in Java
Key: JRUBY-1235
URL: http://jira.codehaus.org/browse/JRUBY-1235
Project: JRuby
Issue Type: Bug
Components: Core Class
I am against such a move. I would love to have some of the features in
Java 5, but the fact of it is that most "enterprises" are still on 1.4.
I believe JRuby is very important especially in the areas where
conservative values reign, and moving to Java 5 will totally destroy
that advantage.
I want you to rename gem to jgem.
--
Key: JRUBY-1234
URL: http://jira.codehaus.org/browse/JRUBY-1234
Project: JRuby
Issue Type: Wish
Affects Versions: JRuby 1.0.0
Reporter: ksaito
For what it's worth, there's been a similar discussion about Scala
and Java 5 over on the Scala mailing list.
The key reason for keeping Scala @ 1.4 is that there is no Open
version of Java 5+ Yes, Sun has open sourced 95% of the JDK, but the
other 5% bars folks from actually releasing an
+1
2007/7/24, Charles Oliver Nutter <[EMAIL PROTECTED]>:
- Annotations for specifying method bindings. This could largely
eliminate the need for manual method-binding code, as well as allow us
to split method implementations by arity and even argument type
I really like this idea.
As we know,
11 matches
Mail list logo
