Re: readpipe patch again

[Akim Demaille]

>>>>> "Paul" == Paul Eggert <address@hidden> writes:

Paul> The current Bison CVS has a bug: it creates a temporary file to
Paul> feed to m4, but it doesn't clean up the file if interrupted.

Well, I wouldn't call this a bug: it is an area which still needs
work, but we know that :)


Paul> The simplest way that I can see to fix the problem is to modify
Paul> Bison to not create a temporary file at all: instead, Bison can
Paul> just write to a pipe and have m4 read from that pipe.

Why not.  But it must remain possible, at least for debugging, to
bison to save this file.  That's the reason why I chose a file.


Paul> So this raises the question: how important is it to run Bison on
Paul> hosts that lack `fork'?  Such hosts are not GNU hosts; nor are
Paul> they Unix hosts; nor are they POSIX hosts.  One could argue that
Paul> a developer should have access to a GNU or Unix or POSIX host to
Paul> run Bison on, even if the rest of the build runs on some other
Paul> host.

I have no big problem with that myself, but ISTR there were people
wanting to use Bison under DOS.  Hm.  Can't make up my mind :(