Does Ruby suffer from the same problems as "dll hell"?
How does Ruby 1.8.2 handle different versions of 3rd party ruby modules being required by different scripts?
Do 3rd party ruby module names need to include version numbers when they become incompatible with prior versions?
Ruby does not yet have a built-in solution for library versioning
issues. There are a couple of third-party approaches that may
ultimately find their way into Ruby at the core, but they are not
feature complete and matz has not indicated one way or another except
that they must meet the usual level of quality.
-austin
On Sat, 31 Jul 2004 03:31:42 +0900, H. Simpson <nospam@asdlkfjhasldkjfsadlfhskadjfahsldfks.com> wrote:
Does Ruby suffer from the same problems as "dll hell"?
How does Ruby 1.8.2 handle different versions of 3rd party ruby modules
being required by different scripts?Do 3rd party ruby module names need to include version numbers when they
become incompatible with prior versions?
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca