It optimises well because it assumes/requires no aliasing. You can/could always alias by passing a variable (or an array) into a function twice. That is: f(a,a)
This is illegal under the spec (at least up to F77), and the optimisers could work on the assumption that the variables were distinct.... a much easier job.
Of course, using EQUIVALENCE could introduce the same type of aliasing.
ITRW, should you be involved in litigation, the opposing attorney will ask for any and all files that may contain something relevant to the issue at hand.
I once worked for a firm that had to turn over 1.5+ years of all R&D + financial records -- for an indeterminant period of time.
The cost of assembling those records was huge.
The idea of going months or years without them was impossible, which lead to the additional cost of copying them.
After that experience, I have reviewed my files once per year. If I really need it, I keep it. If I don't really need it, it gets tossed.
It is not a question of hiding things. It is a question of avoiding a bigger burden down the line.
One sure sign of a decaying civilization (according to the old Azimov 'Foundation' series) was the trend of researchers to re-analyize other's work, instead of doing the research themselves...
This should not be a surprise.
The Dartmouth Time Sharing System (DTSS) was written in the late 1960s - early 1970s entirely by students. Old mainframe technology (GE/Honeywell) that supported 300 users at a time.
The same group coded the first implementations of BASIC.
To paraphase a patent lawyer friend: Whenever there is a question of reasonableness or prior art, this administration is happy to have the patent office grant the patent and let the courts (read trial lawyers) sort it out.
>3. I'm not a Java newbie. I learned it 5 years ago
Since Java was released less than 5 years ago, are you a member of the original team? Or are you displaying the same pension for accuracy displayed in the original post?
The language was originally designed for the embedded, standalone device market. The original effort was a C++ compiler, but the Green Team decided C++ was not a good language for that product space. Java was a C++ like language with the most error prone features taken out.
The requirements of the embedded, standalone market closely match those of a networked, distributed world, and that has made all the difference in Java's acceptance.
Slashdot Mirror
You can/could always alias by passing a variable (or an array) into a function twice. That is:
f(a,a)
This is illegal under the spec (at least up to F77), and the optimisers could work on the assumption that the variables were distinct.... a much easier job.
Of course, using EQUIVALENCE could introduce the same type of aliasing.
I once worked for a firm that had to turn over 1.5+ years of all R&D + financial records -- for an indeterminant period of time.
The cost of assembling those records was huge.
The idea of going months or years without them was impossible, which lead to the additional cost of copying them.
After that experience, I have reviewed my files once per year. If I really need it, I keep it.
If I don't really need it, it gets tossed.
It is not a question of hiding things. It is a question of avoiding a bigger burden down the line.
One sure sign of a decaying civilization (according to the old Azimov 'Foundation' series) was the trend of researchers to re-analyize other's work, instead of doing the research themselves...
There used to be vineyards in England.
It takes something of an enviromental Luddite to assume that any change from [pick the year of your birth] *must* be fought be any means possible.
This should not be a surprise.
The Dartmouth Time Sharing System (DTSS) was written in the late 1960s - early 1970s entirely by students. Old mainframe technology (GE/Honeywell) that supported 300 users at a time.
The same group coded the first implementations of BASIC.
To paraphase a patent lawyer friend: Whenever there is a question of reasonableness or prior art, this administration is happy to have the patent office grant the patent and let the courts (read trial lawyers) sort it out.
Taxation should serve a purpose:
to provide infrastructure
to provide services
I see no discussion of the purpose of these taxes.
Since Java was released less than 5 years ago, are you a member of the original team?
Or are you displaying the same pension for accuracy displayed in the original post?
The language was originally designed for the embedded, standalone device market. The original effort was a C++ compiler, but the Green Team decided C++ was not a good language for that product space.
Java was a C++ like language with the most error prone features taken out.
The requirements of the embedded, standalone market closely match those of a networked, distributed world, and that has made all the difference in Java's acceptance.