Patrik,

1) *LIBL searches for all called upon objects. Path only accesses executables.

2) Additionally, AFAIK, there are no built in tools to manipulate the path on Windows. You can basically set or replace it.

3) I suppose I should have said "the proper approach" instead of "alternative."

-mark

On 9/18/2024 3:36 PM, Patrik Schindler wrote:
Hello Mark,

Am 18.09.2024 um 19:13 schrieb mlazarus<mlazarus@xxxxxxxxxxxx>:
The *LIBL is a wonderful feature that is unmatched on Unix and Windows platforms. The path environment variable is a poor substitute.
Please elaborate. I can't see where both facilities are substantially different in nature.

The alternative is to have a proper authority scheme on your objects.
This is not exactly an alternative but should be the standard measure.

:wq! PoC


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.