RE: [MiNT] /proc

["Julian Reschke" <reschke@muenster.de>]

> > > environment string. What's the difference between these and
> > > SLBPATH anyway??
> >
> > That's easy to answer. The SLBPATH is inherently
> > process-local. For instance
> > it should allow to put the current directory in front of the
> > path list to
> > enable testing of a local (new) copy of an SLB without
> > touching the original
> > one.
>
> In that case, wouldn't it be easier to use something like...
>
> if (!slb_open(.... "d:\\foobar\\mylib.slb" ....))
> {
>    slb_open(".... "mylib.slb" ....);
> }

The whole point is to allow the (static) client code to be minimal. He
really should only specify the name of the library.