🚀 go-pugleaf

In article <1510@wet.UUCP> naga@wet.UUCP (Peter Davidson) writes:
>[Ban vi!]  When using two function libraries the Microsoft compiler
>manual says to set the LIB environment variable to include both
>paths separated by a semicolon.  But when one tries to 
>SET LIB=\C\LIB;\C\OTHERLIB DOS (as usual) treats the semicolon
>as a command separator and rejects the second part.  Is this
>another Microsoft linker feature, or is there some way to set
>up the LIB variable (from the DOS command line) as required?

Eh?  DOS does not usually come with a "command separator" capability.

Do you have ANARKEY or 4DOS loaded?  If so, then that's likely where
the problem is.

DOS uses semicolons in the PATH variable, and millions of DOS users have
no problems setting this variable.  If you are using 4DOS, then switch your
command separator character to ^ (the default?).  With ANARKEY, you are 
more out of luck.  I think you have to prefix it with something each time..
This is mentioned in the .DOC file somewhere.
-- 
 ___Mark S. Lord__________________________________________
| ..uunet!bnrgate!mlord%bmerh724 | Climb Free Or Die (NH) |
| MLORD@BNR.CA   Ottawa, Ontario | Personal views only.   |
|________________________________|________________________|