John Plocher wrote:
> Chris Pickett wrote:
> >> Last but not least what is a shell ? would /usr/lib/shell/python be
> >> allowed ?
> >
> > Don't. Be. Silly.
> > http://en.wikipedia.org/wiki/UNIX_shell
> >
> > Unless python starts calling itself a shell it isn't one.
>
> What "libraries written in a scripting language" have to do
> with "shell" is exactly the point. Python is a scripting
> language, it has reusable libraries, people are reputed to
> have written useful things in it, and, like Tom Christianson
> and Perl, I'm sure someone has actually tried using the Python
> interpreter as their login shell at least once :-)
>
> Given Roland's suggested usage model (a place to put compiled
> ksh93 scripting language libraries for use by others), the name
> he chose for the directory (.../shell) seems to be too generic,
> and thus out of place.
Point was: Bundle the shell function libraries _toegether_ in one common
base directory, have them share functions via ${BASEDIR}/sh/ if the
functions are in the POSIX shell syntax and in interpreter-specfic (e.g.
${BASEDIR}/zsh/..., ${BASEDIR}/ksh/...) if they use extended syntax...
and handle the modules (one module may contain multiple functions) and
functions in a DNS-like hieracy and allow pattern to be used as
selectors.
<rant>Why is this /usr/lib/shell/ directory _that_ difficult_ to get via
ARC ? Somehow I'm starting to regret to have exposed too much detail and
now we're _bickering_ (sorry for that word but I don't know any better
word for it) the details down to a sub-atomic level to hell.</rant>
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
