Re: 'read ... < file' works, but horks up subsequent executions

[Chet Ramey]

> Previous experience with the read builtin had convinced me that its
> limitations made it almost useless, and section E4 of the Bash FAQ backed
> this feeling up.  Then I found myself needing to split input up and store
> it in successive variables (since arrays can't be exported, and 'export'
> won't even print an error if you try).  So I decided to give 'read' one
> more chance, because that's exactly what it's supposed to do.
> 
> It's almost working, but about to re-convince me that it really is useless.

You don't say which version of bash you're using, but I can't reproduce
this in 2.05b running on MacOS X, FreeBSD, or Linux.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
                                                Live...Laugh...Love
Chet Ramey, ITS, CWRU    chet@po.cwru.edu    http://tiswww.tis.cwru.edu/~chet/