www.delorie.com/archives/browse.cgi | search |
Sender: | nate AT cartsys DOT com |
Message-ID: | <36365C8B.43A03AF6@cartsys.com> |
Date: | Tue, 27 Oct 1998 15:51:39 -0800 |
From: | Nate Eldredge <nate AT cartsys DOT com> |
X-Mailer: | Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i486) |
MIME-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
Subject: | Re: Parse errors |
References: | <4af57b8d DOT 36227988 AT aol DOT com> <Pine DOT OSF DOT 4 DOT 05 DOT 9810122353150 DOT 5384-100000 AT sable DOT ox DOT ac DOT uk> <703q7p$bus$1 AT nnrp1 DOT dejanews DOT com> <Pine DOT BSF DOT 4 DOT 05 DOT 9810230201470 DOT 22326-100000 AT localhost> <36310D20 DOT CE9344A0 AT cartsys DOT com> <714o6t$jej$1 AT nnrp1 DOT dejanews DOT com> |
Reply-To: | djgpp AT delorie DOT com |
silkwodj AT my-dejanews DOT com wrote: > > Memory errors cause a lot of other problems that are hard not to notice. I > had this kind of problem once and it was like having a virus. Large > executables that were copied to zip drives were wrecked just as I thought I > was archiving. Not always, though. On my Linux system I'm having irreproducible GCC crashes once every few months and I'm a little worried... > Well, anyway my original parse errors were eventually found. Good! Glad you solved it. -- Nate Eldredge nate AT cartsys DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |