2 ms·
At this point, it's not necessarily just an alternate syntax. Given that, #langs can be interoperable, and are encouraged to be, but not necessarily. For a si
by neilv 7y ago
At this point, it's not necessarily just an alternate syntax.
Given that, #langs can be interoperable, and are encouraged to be, but not necessarily.
For a simple real-world example of interoperability problems, of the kind we could plausibly encounter between two very similar #langs... Consider that RnRS Scheme wants to use mutable lists, but modern Racket wants to use immutable lists. Code in the two #langs might even look almost identical, and even use the same names and calling conventions, but in practice you have trouble interoperating.
There's also factors like: what syntax is in the documentation everyone reads. If all the manuals people see are in a new syntax, the old syntax effectively becomes a dying language, whether or not it's still implemented.
With priorities and/or work, we can support a high degree of interoperability, as well as keeping the current syntax genuinely supported, but we shouldn't assume we get that for free. Nor should we assume it will happen, unless we make it a top requirement that's tracked and remains a consideration in every change.