If Java is the new C then how do we make it a better C. (I'm not
being sarcastic). If we don't want to go off on unpredictable
tangents with the language and change it's fundamental principals,
then perhaps we can concentrate on features which reduce our boiler
plate and reduces code size.
How about a new shortcut definition for beans?
public bean Thingy {
String name;
String value;
}
How about some way of doing delegation automatically?
Perhaps we analyze where redundant boiler plate exists commonly and
find ways to short cut it, but be in the style of Java.
We have discussed the chained 'returns this' method invocation - but I
still can't understand why people give that so much credibility. It
imposes strange behavior on an API for the sake of code density. When
a 'using' operator would perform the same function, globally and
backwards compatible.
I had thought for a moment that we could create an operator to
shortcut reflection.. But the problem there I guess is that people
would actually use it (and abuse it). Or is this already coming with
involk dynamic? object->"method"(params, ... );
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---
