Article View: comp.sys.next.programmer
Article #1493Re: printf g format still broken under NeXTSTEP 3.0
From: felix.lugo
Date: Wed, 11 Nov 1992 03:33
Date: Wed, 11 Nov 1992 03:33
11 lines
955 bytes
955 bytes
In article <1992Nov11.012228.23372@access.usask.ca> eric@skatter.usask.ca writes: | I reported this bug in December 1989, and when NeXTSTEP 2.0 came out, | and when NeXTSTEP 2.1 arrived, and now that NeXTSTEP 3.0 has arrived ... | IT STILL ISN'T FIXED!!!!! | I thought compiler problems were supposed to be reported to the GNU people. This one certainly fits that category! BTW, GCC 2.1 generates the same output as (NeXT 3.0) GCC 1.93. --Felix
Technical Details
Message-ID:
<1992Nov11.033324.9278@cbnewsl.cb.att.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!news.tek.com!psgrain!charnel!rat!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsm!cbnewsl!cocoReferences:
<1992Nov11.012228.23372@access.usask.ca>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!news.tek.com!psgrain!charnel!rat!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsm!cbnewsl!coco From: coco@cbnewsl.cb.att.com (felix.lugo) Subject: Re: printf g format still broken under NeXTSTEP 3.0 Organization: AT&T Date: Wed, 11 Nov 1992 03:33:24 GMT Message-ID: <1992Nov11.033324.9278@cbnewsl.cb.att.com> References: <1992Nov11.012228.23372@access.usask.ca> Lines: 12