Russel Winder wrote:
There is currently a big debate in the Groovy mailing list about
<expression> if <condition>
<expression> unless <condition>
constructs into the language.
So, they've solved all the important problems with the language, then?
Anyone familiar with Perl or Ruby will
have come across this "condition after expression" construct.
If they do introduce them (and personally, I'd be in favour),
make sure they don't end up in the position that Ruby is in,
foo if bar;
if bar then foo end;
can have different semantics. See here for more info:
Of course, if they want ultimate freedom of expression, they
ought to sanction:
if foo then bar else baz end unless quux;
Severely confused programmers all round!
Frank Wales [EMAIL PROTECTED]