Rod Evans <rie at eng.sun.com> wrote:
> Presently, no. But it seems like a mechanism to allow ':' within
> a path is now desirable.
>
> I've a couple of thoughts. First, if you wish to allow ':' within
> a dlopen() path, would you also want to allow this character in
> a RUNPATH, LD_LIBRARY_PATH, or some other ld.so.1 processed path?
> We could invent an escape character that can be embedded in a path.
> This provides generic flexibility, but in the case of dlopen()
> might require the user to translate a string (read from some config
> file?) to include the escape character.
>
> Or, we could allow dlopen() path processing to differ/be-more-flexible
> than other path processing. We could force a dlopen() string to be
> used as-is. This changes todays behavior, and would break the example
> I had cited below. But, would anyone care? Or we could be explicit
> in regards our new requirement:
>
> dlopen("foo:bar", RTLD_LAZY | RTLD_FULLPATH)
>
> and use a new token to define a path should be used as is.
let us look at the standard....
The file argument is used to construct a pathname to the object file.
If
file contains a slash character, the file argument is used as the
pathname
for the file. Otherwise, file is used in an implementation-defined
manner
to yield a pathname.
See http://www.opengroup.org/onlinepubs/009695399/functions/dlopen.html
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
