fix-2 gcc patch implications?

Article View: comp.windows.x

Article #36849

#36849

From: David Kaelbling
Date: Wed, 14 Feb 1990 20:14

10 lines
877 bytes

I notice that fix #2 contains a work-around for the gcc XtNewString
bug.  Does this mean that gcc-1.36 or some newer release has been
blessed as "safe for those of us who don't know adb and are happy that
way"?  Previous postings led me to believe that only gcc-1.35 had been
tested and was considered trustworthy...
--
David Kaelbling                                       (408) 496-3600
c/o Rational; 3320 Scott Boulevard; Santa Clara, CA       95054-3197
Email: drk@Rational.COM, or uucp {uunet,ubvax,amdcad,aeras}!igor!drk

Technical Details

Message-ID: <600@igor.Rational.COM>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!lll-winken!ubvax!igor!twinkie!drk

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!lll-winken!ubvax!igor!twinkie!drk
From: drk@twinkie.Rational.COM (David Kaelbling)
Newsgroups: comp.windows.x
Subject: fix-2 gcc patch implications?
Keywords: fix-2,gcc
Message-ID: <600@igor.Rational.COM>
Date: 14 Feb 90 20:14:21 GMT
Sender: news@Rational.COM
Lines: 10