On May 15, 2007, at 12:30 PM, Brandon Van Every wrote:
On 5/15/07, Peter Keller <[EMAIL PROTECTED]> wrote:
I don't think there is ANYTHING that anyone can do which is the right
answer since you basically have to bail at *runtime* if the linker
loader
notices two APIs of the same kind clashing in the program.
I thought C# had a strong notion of versioning. I haven't really
gone up the C# learning curve enough to recall whether an Assembly
is a C# or a .NET concept though. Nor whether it provides an
ultimate solution.
Been a few years since I used C# but I think the Assembly is .NET
(Yes it is - http://en.wikipedia.org/wiki/.NET_assembly).
MacOS X two-level namespace also supplies a finer grained library
versioning. (& bundles+frameworks are similar in purpose to a .NET
Assembly. The missing security aspect is glaring though.)
Don't know if Java solves it either.
The theme is to put versioning in the language though.
Cheers,
Brandon Van Every
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
