Path: utzoo!attcan!uunet!ginosko!usc!bloom-beacon!athena.mit.edu!jstravis From: jstravis@athena.mit.edu (John S. Travis) Newsgroups: comp.windows.x Subject: Re: Linking Libraries/Undefined variables Summary: tempnam Message-ID: <13592@bloom-beacon.MIT.EDU> Date: 17 Aug 89 23:51:28 GMT References: <3930009@hpcll01.HP.COM> <13489@bloom-beacon.MIT.EDU> <1687@bacchus.dec.com> <2369@auspex.auspex.com> Sender: daemon@bloom-beacon.MIT.EDU Reply-To: jstravis@athena.mit.edu (John S. Travis) Organization: Massachusetts Institute of Technology Lines: 20 In article <2369@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes: > - >> You are correct. Tempnam/Tmpnam is a routine in HP-UX C library that lets - >> you create temporary files. It is strange that HP Widgets would use a routine - >> that is not standardly available ... - -BSD has "tmpnam", and S5 has "tempnam" and "tmpnam". I don't know -which, if any, of them were in the AT&T UNIXes from which both BSD and -S5 were derived.... - -"tmpnam" is in POSIX, and "tempnam" isn't. Given that, it would -probably be a good idea to avoid using "tempnam" if you possibly can, -since it's less likely to be available in any particular system. The original problem is that the HPWidgets call the function, not the application programmer. Although, i just wrote a makeshift function of the same name, and it seems to do the job, i'm surprised HP did this. john travis