🚀 go-pugleaf

In message <4eqijl$j3b@nnrp1.news.primenet.com> - gfraley@primenet.com writes:


In <4eq0lc$k4c@lyra.csx.cam.ac.uk>, rdhw@cus.cam.ac.uk (Robin D.H. Walker) writes:
>>>: SET BEGINLIBPATH & SET ENDLIBPATH statements.  Using these statements, you
>>>: can dynamically expand/contract the LIBPATH statement.
>>
>>Where is this documented?
>>-- 
>>Robin Walker         (Network Admin), Queens' College, Cambridge, CB3 9ET, GB
>>rdhw@cam.ac.uk   IBMmail:i1006437   Tel:+44 1223 335528   Fax:+44 1223 335566

>I found it in several external books on OS/2.  OS/2 WARP Uncensored is an
>excellent resource, as it is co-authored by two of the developers.


I think perhaps you mean Warp Unleashed. I have just checked and 
indeed  this is documented on page 66. I also learnt something else 
from another tip on this page. I quote:   
  
You can improve performance if you keep the various paths as short as 
possible. Many applications suggest adding the directory location to the 
PATH statement. Doing so might help you keep things separate but it 
won't help  performance   
  
Don't add directorys to any path statement unless you need to be able 
to access the programme from the command line. If you establish a 
programme reference object so that you can start the programme from 
the desktop use the "Working directory" setting on the parameter 
setting page.   
  
End of quote.   
  
I post this in case there are others that were  unaware of the above. I 
am off now to prune my enormous PATH statements... 

David