+1
On May 19, 2008, at 6:27 AM, Jacopo Cappellato wrote:
It would be great to see this migration implemented soon.
In my opinion, the priority could be this:
1) change the best practice recommendation
2) migrate (with minimal changes/work) all the existing .bsh scripts
to .groovy scripts
I think this step would be fairly easy - just rename all of the .bsh
scripts to .groovy - however a catch with our existing scripts is that
when you have a script fragment with no class declaration, the script
name becomes the class name, e.g. category.bsh becomes category and
then you can't have an untyped variable named "category" in that
script, since it conflicts with the class. The suggested workaround is
to not use lowercase filenames (switch to Category.groovy) or to
explicitly type the category variable.
3) clean and improve the migrated scripts to take full advantage of
the new language
We could implement #1 and #2 very soon in one big batch, while #3
could be done over time (unless we can bulk change some of the code
in the scripts).
Jacopo
