On 5/17/10 20:35, Nick Sabalausky wrote:
"Sean Kelly"<s...@invisibleduck.org> wrote in message
news:1012172047295742031.093272sean-invisibleduck....@news.digitalmars.com...
BCS<n...@anon.com> wrote:
Hello BCS,
Hello Walter,
BCS wrote:
My program imports lib A and B. Lib A imports lib C and asks
for
version "X". Lib B imports lib C and asks for version "!X". Who
wins?
Compilation error.
Exactly. If there were a way for A to ask for X or Y and B to ask
for
Y or Z than the solution is easy: Y.
And to finish the thought; a system that only allows a program to ask
for a single version is worse than one that doesn't allow any or
allows many.
How does . NET work? I recall versioning being an integral part of the
design.
IIRC, When MS said that, it turned out they were really just talking about
things like "depricated" keyword and designing the OO polymorphism so that
changing one thing won't accidentally break something else (ex: manditory
"override" keyword when overriding a base class function). I found it
confusing too that they referred to that as "versioning".
Isn't it possible to put some version information in the binary? Found
this: http://msdn.microsoft.com/en-us/library/4w8c1y2s.aspx
