Re: Closures

The Java scripting domain!

As long as the language *extends* Java like Pat suggests in the other 
mail, your concern should be taken care of. The syntax sugar I had in 
mind was closures and unification of syntax for arrays and collections 
including initialization.

-Harish

Curt Cox wrote:

> What domain is that?
>
> The appeal that BeanShell holds for me is that it is trivial to move
> code back and forth between BeanShell and Java.  The beauty of
> supporting the Java language is that it is an established standard.
>
> The problem with any particular bit of sugar is that it hampers this
> movement.  Personally, I would like Java to unify the syntax for
> arrays, lists, maps, and sets.  Until that happens, I would be
> reluctant for it to occur in BeanShell for fear that the implementations
> wouldn't be completely compatible.
>
> At first blush, all blocks supporting finally seems sensible.
> http://nick.chalko.com/smc2/blog/tech/Java/?permalink=AutoTryBlock.txt
>
> Sugar is a tree with many branches.
>
> Harish Krishnaswamy wrote:
>
>> I agree that the code will become hard to read when you add a lot 
>> Perl-ish syntax, but there is a lot of other intuituve syntax that is 
>> absent in Java. That is the primary reason people are allured to it. 
>> It makes the code concise and to the point which helps readability 
>> and productivity. Besides it is a pleasure to code. I think Beanshell 
>> should consider a lot of the syntax sugar that Groovy is adding if it 
>> would like to continue playing in this domain.
>>
>> -Harish
>>
>> Mark Swanson wrote:
>>
>>> -1
>>>
>>> I only want Java syntax with as little scripty features as possible. 
>>> The thing that appeals to me the most about BeanShell is that it 
>>> aims to provide embedable scriptable Java. I believe adding 
>>> Icon/Eiffel/Python/etc... features would make the language so 
>>> difficult to learn people won't bother. I look at the language 
>>> features Groovy is incorporating and I know that I'll likely never 
>>> find the time to understand them, and I'll likely never be able to 
>>> read Groovy code that uses them. I want to stick with what I'm 
>>> comfortable with and that's just plain Java. When I embed BeanShell 
>>> I want to provide people with a scripting language built on a 
>>> well-known and understood syntax - Java.
>>>
>>> Perhaps this issue is what will separate BeanShell and Groovy.
>>>  
>>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
>> For a limited time only, get FREE Ground shipping on all orders of $35
>> or more. Hurry up and shop folks, this offer expires April 30th!
>> http://www.thinkgeek.com/freeshipping/?cpg=12297
>> _______________________________________________
>> Beanshell-developers mailing list
>> Beanshell-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/beanshell-developers
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> http://www.thinkgeek.com/freeshipping/?cpg=12297
> _______________________________________________
> Beanshell-developers mailing list
> Beanshell-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/beanshell-developers
>


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297