bug in bison (1.01)

Article View: gnu.utils.bug

Article #1657

#1657

From: Ron Guilmette
Date: Mon, 05 Jun 1989 23:15

11 lines
777 bytes

I believe that bison (1.01) fails to actually do an "unlink"
on its output file if that file exists already.

Unfortunately, if the output file *does* already exist, and
if there are one or more hard links to it (other than the
output file itself) then Bison's unwillingness to actually
unlink before writting to the output file can causes
undesriable (and perhaps even disasterous) consequences.

// rfg

Technical Details

Message-ID: <8906052315.AA02299@pink.aca.mcc.com>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!MCC.COM!rfg

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!MCC.COM!rfg
From: rfg@MCC.COM (Ron Guilmette)
Newsgroups: gnu.utils.bug
Subject: bug in bison (1.01)
Message-ID: <8906052315.AA02299@pink.aca.mcc.com>
Date: 5 Jun 89 23:15:13 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 11