Date: Sun, 12 Jul 1998 01:14:27 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: cyouse@artemis.syncom.net (Charles Youse) Cc: bakul@torrentnet.com, joelh@gnu.org, dchapes@ddm.on.ca, rminnich@Sarnoff.COM, hackers@FreeBSD.ORG Subject: Re: Improvemnet of ln(1). Message-ID: <199807120114.SAA17113@usr08.primenet.com> In-Reply-To: <Pine.NEB.3.96.980711114048.7449A-100000@artemis.syncom.net> from "Charles Youse" at Jul 11, 98 11:46:54 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > For interactive use, alias ln to `ln -w' to warn you. If you
> > change the default behavior of ln, you *will* break scripts.
> > Unlike editors, ln is more likely to be used in scripts than
> > interactively (well, it is so for most people).
>
> I fail to see how. An extra line output to stderr is going to break
> scripts? Can you provide an example?
...
# call subscript, save all output... a successful subscript will produce
# no output...
OUT=/tmp/out.$$
subscript > $(OUT} 2>&1
# postprocess output to look for errors, warnings...
...
echo "The following failures occurred while processing subscript:"
echo "-----------------------------------------------------------"
cat ${OUT}
echo "-----------------------------------------------------------"
rm ${OUT}
exit 1
fi
> > Bottom line: backward compatibility is a good program design.
>
> Well, not always. Compare Windows/DOS.
That's OS design, not program design. Most code can be compiled on
Windows/DOS, if only because, by definition, good program design means
the code is portable to diverse platfroms, including Windows/DOS.
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807120114.SAA17113>