Re: Hacking BeanShell with JavaCC

No code war needed.  Language is a matter of personal preference, and I
assume people on this list are here because they prefer BeanShell to Groovy. 
I was just expressing my opinion.  Operator overloading should be added in a
clean way to BeanShell.  I have been adding to BeanShell beyond Java 1.3/1.4
in my BeanShell fork here:

http://code.google.com/p/beanshell2/



Stevenson, Scott W wrote:
> 
> CODE WAR?  Ohh it's on baby!
> 
> Some of us REALLY like the way Groovy does operator overloading.
> Programming by convention is the next big thing.  The Groovy way lets
> you plug in pure java classes and still take advantage of operator
> overloading.  Groovy has all the best features of Java, BeanShell, Ruby,
> and Python; while doing an excellent job of leveraging the full power of
> Java.  As for Python, I can't stand that the syntax is tab/whitespace
> dependent.  BeanShell is good if you just want a small embeddable
> interpreter, but it stopped evolving somewhere around Java 1.3/1.4.
> 

-- 
View this message in context: http://www.nabble.com/Hacking-BeanShell-with-JavaCC-tp16715411p16732310.html
Sent from the BeanShell - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone