Subject: Re: A patch to add builtin read (small bug)
Date: Thu, 23 Sep 1993 12:03:47 -0400 [thread overview]
Message-ID: <9309231607.AA09004@SINet.SLB.COM> (raw)
In-Reply-To: Your message of "Thu, 23 Sep 1993 17:28:11 +0200."
|At least one of those bug fixes I mentioned prevents a crash, you really
|should look into them.
Ok, someone has a "jumbo" patch against a vanilla 1.4 ? (saves me from
scanning the archive for the actual patches).
|[ Re: read x;eval 'x=('$x')']
|Yeah, it's a stunt, and I should have made the standard disclaimer that
|pathalogical cases would kill it.
A hopefully not_so_pathological example:
The password file may have * in the password field for some special
users, which gets expanded to all files in the current directory...
|[ Re: ifs aware read function]
|Because you lose information that you can't get back. For example if
|you are trying to parse the entries from /etc/passwd to find the home
|directories, and the comment field is blank:
|[example with blank fields deleted]
|and when you try to retrieve $x(6) which should be the directory you get
|/bin/rc instead! This may not be the worlds best example but I hope my
|point is clear. The way read works now preserves potentially important
Ok, good example, but an ifs aware read still allows you to set ifs to
newline before reading, giving you the functionality of the current read.
The risk of loosing information is my responsability I think, it is not
up to the read function to keep me from doing so.
J.G. Vons E-Mail: firstname.lastname@example.org
next reply other threads:[~1993-09-23 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-23 16:03 gjv%atlas%cesar [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-23 18:10 Tom Culliton x2278
1993-09-23 15:36 Arnold Robbins
1993-09-23 15:19 Tom Culliton x2278
1993-09-23 7:30 gjv%atlas%cesar
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).