Ultrix 3.0 changed basename(1)

[Maarten Litmaath]

frank at riscy.dec.com (Frank Wortner) writes:
\In article <3074 at solo4.cs.vu.nl> maart at cs.vu.nl (Maarten Litmaath) writes:
\=mjb at acd4.UUCP ( Mike Bryan          ) writes:
\=\It seems basename() now does some limited regular expression handling.
\=\Therefore, the command "basename /vmunix .x" will produce "vmun",
\=\rather than the expected "vmunix".  [...]
\=
\=To whoever made this change: the abovementioned behavior is COMPLETELY
\=DISTURBED!  It's like: in Ultrix 3.0 the kernel will reside in /bin/cat!
\=Use /etc/fsck to catenate files. :-(
\
\If you are as upset as your message seems to indicate, let me ask:
\Has anyone submitted an SPR regarding this problem?  That is the way
\bugs get reported.

Let me clarify.  We don't use Ultrix at all!  So don't expect a bug report
from me, other than in comp.unix.ultrix.
On the change: the regular expression addition is a good idea IN PRINCIPLE.
However, instead of making it the DEFAULT (is there a way to turn it off?),
the implementors should have added an option like `-e', that is

	$ basename -e /vmunix .x
	/vmun
	$ basename /vmunix .x
	/vmunix

Another possibility is a NEW program, like `ebasename', for Extended basename.
This utility could be a link to the old `basename', which would check its
argv[0] to find out the intended behavior.
-- 
C, the programming language that's the same |Maarten Litmaath @ VU Amsterdam:
         in all reference frames.           |maart at cs.vu.nl, mcvax!botter!maart