>> The `L.so' in this case should probably follow the naming scheme we
>> adopted for the `.so' files that Class.forName will automatically try
>> to load. That will make it so that the linker and Class.forName will
>> agree -- it won't matter to the end program whether a class is loaded
>> at runtime or at link time.
Per> Do you have a write-up of this?
Nothing formal :-(.
Here is the comment in natClassLoader.cc:
// Turn `gnu.pkg.quux' into `gnu-pkg-quux'. Then search for a
// module named (eg, on Linux) `gnu-pkg-quux.so', followed by
// `gnu-pkg.so' and `gnu.so'. If loading one of these causes
// the class to appear in the cache, then use it.
Tom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
- Re: java library installation issues Per Bothner
- Re: java library installation issues Paul Reavis
- Re: java library installation issues Bill Wohler
- Re: java library installation issues Per Bothner
- Re: java library installation issues Egon Willighagen
- Re: java library installation issues Andrew Pimlott
- Re: java library installation issues Per Bothner
- Re: java library installation issues Egon Willighagen
- Re: java library installation issues Tom Tromey
- Re: java library installation issues Per Bothner
- Re: java library installation issues Tom Tromey
- Re: java library installation issues Per Bothner
- Re: java library installation issues Jeff Sturm
- Re: java library installation issues Tollef Fog Heen
- Re: java library installation issues Egon Willighagen
- Re: java library installation issues Seth Arnold
- Re: java library installation issues Paul Reavis

