Thorsten Behrens wrote:
Michael Meeks <[EMAIL PROTECTED]> writes:
I don't think you can easily make that work again with some env variable:
osl_loadModuleRelative("foo") called from /resolved/path/to/bar.so
causes a dlopen("/resolved/path/to/foo.so").
Sure - the env. var. can clobber / affect what loadModuleRelative does
(and un-relativeize it - or at least make it fall-back to what it used
to do on failure ? ;-)
Yes, please let's have such an (optional) mode. I've always loathed
this silly copying, and it's just another stupid thing to explain to
new developers...
If at all, hacks like symlinking are something for experienced
developers who know exactly the implications of doing this. You should
*never* encourage a newcomer to do such hacks (cf. the blacklist already
present in linkoo).
I would be sad if there was code bloat added to osl just to make that
bad hack work again.
There is too much code in OOo that (explicitly or implicitly) relies on
true colocation of files (for better or worse) to make hacks like
lilnkoo a good idea in the first place.
If we want features like linkoo, first make the code ready for them.
(Maybe I was in a rush when I introduced osl_loadModuleRelative, maybe
some vnd.sun.star.expand:$WHATEVER-PREFIX scheme would be better. I am
very open for discussion about *that*.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
