Re: tmpnam () is _bad_

Article View: comp.sys.next.programmer

Article #422

Back to comp.sys.next.programmer Previous Next

#422

From: Thomas Funke
Date: Mon, 03 Aug 1992 09:33

24 lines
1321 bytes

In article <1992Aug1.195837.2455@reswi.en.open.de> ralf@reswi.en.open.de  
(Ralf E. Stranzenbach) writes:
> Hi,
> 
> i'm using NeXTstep 2.1. Today i noted, that the function "tmpnam ()" is  
not  
> working correctly. See this example:
> 

There are several routines from the runtime-lib which just don't work.  
tmpnam is one of them. Actually it is a 5-line routine, so I really don't  
understand why there is such a bug at all .....

I sent a bug report to NeXT already, and they said they have fixed it in  
3.0. 

Users of CVS beware: You have to hack the sources to make 'cvs patch'  
working !!!

-- 
------------------------------------------------------------------
Thomas Funke  ** E-mail: thf@zelator.in-berlin.de
NeXT-Developer * Unix-Consultant
------------------------------------------------------------------

Technical Details

Message-ID: <1992Aug3.093337.1228@gamelan>

Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!Germany.EU.net!news.netmbx.de!zelator!gamelan!thomas

References: <1992Aug1.195837.2455@reswi.en.open.de>

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!Germany.EU.net!news.netmbx.de!zelator!gamelan!thomas
From: thf@zelator.in-berlin.de (Thomas Funke)
Subject: Re: tmpnam () is _bad_
Message-ID: <1992Aug3.093337.1228@gamelan>
Sender: thomas@gamelan (thomas)
Reply-To: thf@zelator.in-berlin.de (Thomas Funke)
Organization: NNU Corp. - NeXT is Not UN*X
References: <1992Aug1.195837.2455@reswi.en.open.de>
Date: Mon, 3 Aug 1992 09:33:37 GMT
Lines: 24

Reply to Parent Message