Date: Thu, 30 Mar 2000 19:37:01 +1000 From: Sue Blake <sue@welearn.com.au> To: Doug Barton <Doug@gorean.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Proposed new Bourne shell init files Message-ID: <20000330193658.V69444@welearn.com.au> In-Reply-To: <38E2F801.548AAAF1@gorean.org>; from Doug Barton on Wed, Mar 29, 2000 at 10:45:21PM -0800 References: <38E2F801.548AAAF1@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 29, 2000 at 10:45:21PM -0800, Doug Barton wrote:
<many good comments and suggestions snipped>
> Commentary on my files. . . Using allexport instead of an explicit
> 'export' for every variable makes the file easier to read, and gives a
> novice user one less thing to worry about.
I see your point, and offer an alternative view.
I don't consider myself a novice user, but when I was I'd heard of
export, yet I've still not heard of allexport until your email.
(OK, I probably read about it and ignored it).
My fear would be that turning something on in one part of the file and
off again later is likely to assist novices to shoot themselves in the
foot by removing only one of these lines. In one sense it simplifies,
but it does so by making the file's structure more complex. Not too
much so, but avoidable. The multiple exports take up more space and
don't look as clever, but their purpose is crystal clear and one goof
doesn't ruin the lot of them.
It would be a good addition to a separate file with lengthy comments,
supplied as an alternative and/or learning exercise. I might pinch
your idea for that one day :-)
--
Regards,
-*Sue*-
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?20000330193658.V69444>