On Wed, 10 May 2006 01:42, Gregg Townsend wrote:
> The Icon implementation needs to remain stable, so for it a massive
> renaming of environment variables is not possible.
>
> I would be interested in hearing more details about the problem
> beyond "doesn't work". My understanding is that FPATH is a read-only
> variable to ksh.
No, $FPATH is a path to look for pre-declared functions. In older ksh, you
had to do something like
set -fu ftnname # may be typeset not set..
and then it would look in the directories of $FPATH for an implementation
the first time the function is called. The file was expected to have the
same name and provide a function of the same name, although it was allowed
to have other functions or activity as well.
Recently the $FPATH has been improved so that you don't need to pre-declare
your functions as long as $FPATH does not overlap with $PATH. The shell now
looks for all commands first as an alias or a function that is already
defined, then in $FPATH if it is set, (caching discovered filenames) and
then finally it searches the $PATH in the usual manner.
As such, $FPATH has always been assignable. I'm not that sure on what bash
does with it, because I consider bash to be somewhat impure (if only they
strove for better compatibility - sigh) but surely bash has to treat it
almost the same way.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
