Multiple .rb versions support

You mean if
A -> B
A -> C
B -> D v.1
C -> D v.2

That would be a problem … but that would be a problem regardless of what
version loading mechanism was in place. The problem’s not any easier
without
a version loading mechanism – a version loading structure could at least
help track down the problem here.

On the bright side, a complaint from the loader at this point would prevent
us from entering the equivalent of dll-hell. It would be nice knowing up
front that the lib’s requirements are conflicting.

···

From: Chris Morris [mailto:chrismo@clabs.org]

“Henderson, Michael D” michael.d.henderson@lmco.com wrote in message news:667ED598F8A2D311981D00508B1223800E6C7131@emss02m04.ems.lmco.com

From: Chris Morris [mailto:chrismo@clabs.org]

You mean if
A -> B
A -> C
B -> D v.1
C -> D v.2

That would be a problem … but that would be a problem regardless of what
version loading mechanism was in place. The problem’s not any easier
without
a version loading mechanism – a version loading structure could at least
help track down the problem here.

On the bright side, a complaint from the loader at this point would prevent
us from entering the equivalent of dll-hell. It would be nice knowing up
front that the lib’s requirements are conflicting.

I think that it is easier for everyone to keep their libraries up to
date in an open-source enviroment. Therefor, I’m not sure if there is
as much of a need for this.

I like the way java lets you deprecate methods, giving people warning
that they need update their codebase. Perhaps setting the interpreter
to emit warnings for using deprecated apis could help solve the
versioning problem in a simpler way?

~ Patrick