home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #26 / NN_1992_26.iso / spool / comp / sys / next / programm / 7139 < prev    next >
Encoding:
Text File  |  1992-11-10  |  1.3 KB  |  32 lines
  1. Newsgroups: comp.sys.next.programmer
  2. Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!news
  3. From: eps@futon.SFSU.EDU (Eric P. Scott)
  4. Subject: Re: printf g format still broken under NeXTSTEP 3.0
  5. Message-ID: <1992Nov11.052341.7657@csus.edu>
  6. Sender: news@csus.edu
  7. Reply-To: eps@cs.sfsu.edu
  8. Organization: San Francisco State University
  9. References: <1992Nov11.012228.23372@access.usask.ca> <1992Nov11.033324.9278@cbnewsl.cb.att.com>
  10. Date: Wed, 11 Nov 1992 05:23:41 GMT
  11. Lines: 19
  12.  
  13. In article <1992Nov11.033324.9278@cbnewsl.cb.att.com>
  14.     coco@cbnewsl.cb.att.com (felix.lugo) writes:
  15. >    I thought compiler problems were supposed to be reported to the GNU
  16. >people.  This one certainly fits that category!
  17.  
  18. No it doesn't.  printf isn't part of the C language (C has *no*
  19. builtin I/O)--it's just another external procedure call to the
  20. compiler.  NeXT isn't using a GNU C runtime library, so the
  21. original poster is attributing blame where it's due.
  22.  
  23. However, if the "problem" really is that ANSI printf and BSD
  24. printf *need* to have different semantics, then NeXT should
  25. extend sprintf's special treatment to the rest of the printf
  26. family.  Breaking compatibility with existing code is *bad*
  27. (something NeXT needs to start taking a lot more seriously).
  28.  
  29. ANSI C is not "better" C--it's simply "different" C.
  30.  
  31.                     -=EPS=-
  32.