Article View: comp.sys.next.programmer
Article #1495Re: printf g format still broken under NeXTSTEP 3.0
From: Eric P. Scott
Date: Wed, 11 Nov 1992 05:23
Date: Wed, 11 Nov 1992 05:23
19 lines
1398 bytes
1398 bytes
In article <1992Nov11.033324.9278@cbnewsl.cb.att.com> coco@cbnewsl.cb.att.com (felix.lugo) writes: > I thought compiler problems were supposed to be reported to the GNU >people. This one certainly fits that category! No it doesn't. printf isn't part of the C language (C has *no* builtin I/O)--it's just another external procedure call to the compiler. NeXT isn't using a GNU C runtime library, so the original poster is attributing blame where it's due. However, if the "problem" really is that ANSI printf and BSD printf *need* to have different semantics, then NeXT should extend sprintf's special treatment to the rest of the printf family. Breaking compatibility with existing code is *bad* (something NeXT needs to start taking a lot more seriously). ANSI C is not "better" C--it's simply "different" C. -=EPS=-
Technical Details
Message-ID:
<1992Nov11.052341.7657@csus.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!newsReferences:
<1992Nov11.012228.23372@access.usask.ca> <1992Nov11.033324.9278@cbnewsl.cb.att.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!news From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: Re: printf g format still broken under NeXTSTEP 3.0 Message-ID: <1992Nov11.052341.7657@csus.edu> Sender: news@csus.edu Reply-To: eps@cs.sfsu.edu Organization: San Francisco State University References: <1992Nov11.012228.23372@access.usask.ca> <1992Nov11.033324.9278@cbnewsl.cb.att.com> Date: Wed, 11 Nov 1992 05:23:41 GMT Lines: 19