3 ms·
> A -> C-v1 and A -> B -> C-v1.1 is a problem in any language. A language that mangles exported symbols with version information can achieve this (with the exc
by kibwen 12y ago
> A -> C-v1 and A -> B -> C-v1.1 is a problem in any language.
A language that mangles exported symbols with version information can achieve this (with the exception of two versions of a lib trying to contest the same global resource). "A" gets the version of "C" that it expects and "B" gets the version of "C" that it expects, with no name resolution conflicts or method lookup ambiguities.
This does require support from the language, though. You need a standard means of mangling symbols, a way to specify version information for each package, a way to qualify package imports with version info, and so on.
- NateDad 12y agoYeah, it's the global resources that are the biggest problem, though. Certainly, if you can namespace everything, then the code itself won't fall over. If you version the URL in Go, you can do that too. Stuff that uses v1 can live along side the stuff that uses 1.1. THey won't be compatible in that you can't pass a v1.Foo into something that wants a v1.1.Foo... but that's not a good idea anyway.