Re: printf g format still broken under NeXTSTEP 3.0

Article View: comp.sys.next.programmer

Article #1890

Back to comp.sys.next.programmer Previous Next

#1890

From: Matthew Dillon
Date: Sun, 22 Nov 1992 19:27

26 lines
1380 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!!!!!
>
>Here's an example program:

    NeXT is not using an ANSI printf() spec.... for example, NeXT's
    printf() does not return the number of characters output and atexit()
    doesn't work if you kill a process with -HUP.  In fact, quite a few
    functions aren't ansi and there seems to be no option to get an 'ansi'
    compatible library.

					-Matt
>--
>Eric Norum			eric@skatter.usask.ca
>Research Engineer		phone: (306) 966-6308
>Accelerator Laboratory
>University of Saskatchewan

--

    Matthew Dillon		dillon@Overload.Berkeley.CA.US
    1005 Apollo Way		uunet.uu.net!overload!dillon
    Incline Village, NV. 89451	ham: KC6LVW (no mail drop)
    USA 			Sandel-Avery Engineering (702)831-8000

Technical Details

Message-ID: <dillon.0riq@overload.Berkeley.CA.US>

Path: arc1-ca.pugleaf.net!sparky!uunet!overload!dillon

References: <1992Nov11.012228.23372@access.usask.ca>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!overload!dillon
From: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Newsgroups: comp.sys.next.programmer
Subject: Re: printf g format still broken under NeXTSTEP 3.0
Distribution: world
Message-ID: <dillon.0riq@overload.Berkeley.CA.US>
References:  <1992Nov11.012228.23372@access.usask.ca>
Date: 22 Nov 92 11:27:16 PST
Organization: Not an Organization
Lines: 27

Reply to Parent Message