Brian Goetz speaks to InfoQ on proposed hyphenated keywords in Java
-
On his continuing quest for productivity and performance in the Java language, Brian Goetz, Java language architect at Oracle, along with Alex Buckley, specification lead for the Java language and Java Virtual Machine at Oracle, proposed a set of hyphenated keywords to evolve a mature language in which adding new features can be a challenge with the current set of keywords as defined in the Java SE 12 Java Language Specification.
Or is that an 'em-dash'?
"Examples of proposed hyphenated classic keywords would include: non-final, break-with, and value-class. Examples of proposed hyphenated contextual keywords would include: non-null, read-only, and eventually-true." I need to figure out how I can work 'eventually-true' into my next program. It's so aspirational.
-
On his continuing quest for productivity and performance in the Java language, Brian Goetz, Java language architect at Oracle, along with Alex Buckley, specification lead for the Java language and Java Virtual Machine at Oracle, proposed a set of hyphenated keywords to evolve a mature language in which adding new features can be a challenge with the current set of keywords as defined in the Java SE 12 Java Language Specification.
Or is that an 'em-dash'?
"Examples of proposed hyphenated classic keywords would include: non-final, break-with, and value-class. Examples of proposed hyphenated contextual keywords would include: non-null, read-only, and eventually-true." I need to figure out how I can work 'eventually-true' into my next program. It's so aspirational.
You forgot, this-is-not-a-loop
-
On his continuing quest for productivity and performance in the Java language, Brian Goetz, Java language architect at Oracle, along with Alex Buckley, specification lead for the Java language and Java Virtual Machine at Oracle, proposed a set of hyphenated keywords to evolve a mature language in which adding new features can be a challenge with the current set of keywords as defined in the Java SE 12 Java Language Specification.
Or is that an 'em-dash'?
"Examples of proposed hyphenated classic keywords would include: non-final, break-with, and value-class. Examples of proposed hyphenated contextual keywords would include: non-null, read-only, and eventually-true." I need to figure out how I can work 'eventually-true' into my next program. It's so aspirational.
Kent Sharkey wrote:
Or is that an 'em-dash'?
Um, no, they're hyphens[^]. But what is the frugging point? If I see a hyphen in a statement, I will automatically think that the value of one variable is being subtracted from the value of another, and will be looking for where the result is to be stored. Talk about utterly useless and confusing "improvements"!
I wanna be a eunuchs developer! Pass me a bread knife!
-
Kent Sharkey wrote:
Or is that an 'em-dash'?
Um, no, they're hyphens[^]. But what is the frugging point? If I see a hyphen in a statement, I will automatically think that the value of one variable is being subtracted from the value of another, and will be looking for where the result is to be stored. Talk about utterly useless and confusing "improvements"!
I wanna be a eunuchs developer! Pass me a bread knife!
Especially since
int res=var1-var2;is valid Java. -
Especially since
int res=var1-var2;is valid Java.Joe Woodbury wrote:
Especially since
int res=var1-var2;is valid Java.The problem couldn't be demonstrated more clearly.
I wanna be a eunuchs developer! Pass me a bread knife!
-
On his continuing quest for productivity and performance in the Java language, Brian Goetz, Java language architect at Oracle, along with Alex Buckley, specification lead for the Java language and Java Virtual Machine at Oracle, proposed a set of hyphenated keywords to evolve a mature language in which adding new features can be a challenge with the current set of keywords as defined in the Java SE 12 Java Language Specification.
Or is that an 'em-dash'?
"Examples of proposed hyphenated classic keywords would include: non-final, break-with, and value-class. Examples of proposed hyphenated contextual keywords would include: non-null, read-only, and eventually-true." I need to figure out how I can work 'eventually-true' into my next program. It's so aspirational.
-
That has to be one of the more idiotic ideas I have read of in a very long time.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Oracle's not managing the language well, IMO.
TTFN - Kent
-
Oracle's not managing the language well, IMO.
TTFN - Kent
-
On his continuing quest for productivity and performance in the Java language, Brian Goetz, Java language architect at Oracle, along with Alex Buckley, specification lead for the Java language and Java Virtual Machine at Oracle, proposed a set of hyphenated keywords to evolve a mature language in which adding new features can be a challenge with the current set of keywords as defined in the Java SE 12 Java Language Specification.
Or is that an 'em-dash'?
"Examples of proposed hyphenated classic keywords would include: non-final, break-with, and value-class. Examples of proposed hyphenated contextual keywords would include: non-null, read-only, and eventually-true." I need to figure out how I can work 'eventually-true' into my next program. It's so aspirational.
Yes! Please do it! As fast as possible! So much the sooner we can jump on the carcass of Java! :-D :-D :thumbsup::thumbsup:
#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun