On Tuesday, August 1, 2017 at 10:18:21 AM UTC+1, Russel Winder wrote
Once a programming language goes into production and invokes "backward
compatibility" it rarely improves by evolution. cf. Fortran, Java.
In principle, a language can improve, if the replacement is
- distinguishable from it's predecessor, and
- there is a correctness-preserving transform.
When I was doing porting ("competitive migration"),
- we didn't have sets of refactorings, which are defined as
correctness-preserving, and
- we had a bit of a kludge for distinguishing dialects. The latter was
"came from AIX 0.9, going to SunOS 5.2"
Now we have versioned dialects, and a class of useful refactorings, so
some changes are possible.
Not trivial, but if they're mechanizable, hardness doesn't matter.
--dave
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
