Comments on: RE: It’s not about one-liners

By: Cedric

Cedric — Mon, 20 Sep 2004 16:25:17 +0000

Totally agree, Glen. Actually, I was thinking of showing an example of properties in Ruby/Groovy to make my point initially. I write so many getters/setters/fields every day in Java that it should be part of the language.

These are one-liners in Groovy, Ruby and C# (and I think I prefer the C# version of all three).

–
Cedric

By: Glen Stampoultzis

Glen Stampoultzis — Mon, 20 Sep 2004 16:10:31 +0000

Dion, not a very good example in this case but overall most of these ’scripting’ languages are a lot less verbose.

Marc, the main point isn’t that the IDE can let you write lots of code quickly it’s how quickly you can interpret it later when reading it back. Less code does not always mean easier to read (ie Perl) but it can. If Java would let me write something like:

property read write int totalCost;

indead of

private int totalCost;

public int getTotalCost()
{
return totalCost;
}

public void setTotalCost(int value)
{
this.setTotalCost = value;
}

it would be reduce the effort in understanding a new class. Obviously one bit of code on it’s own doesn’t create a big problem but when you multiply this by 10 or more properties it starts to make a bigger difference and really this is just one potential way you make things easier.

By: Morten Wilken

Morten Wilken — Mon, 20 Sep 2004 10:55:08 +0000

String name=”Dion ‘Sick Boy’ Almaer”;
name=name.replaceAll(”Sick Boy”,”");