Re: Xwpe 1.5.23a

["Brian K. White" <linut@squonk.net>]

Dennis Payne wrote:
> 
> I've finally gotten around to putting out a new release.  Here's the
> CHANGELOG entry:
> 
> 1.5.23a
> * Added another zoom fix by Mark Spieth
> * XSelection was added to 1.5.22a but forgot to get mentioned in the
>      CHANGELOG.
> * Added Fritz's Y2K patch.
> * Converted info reader to use zlib.  Zlib may be required in the future.
> * Allow tempnam() to create the temporary directory name if available.
>      This function may also be required in future releases.
> 
> Also fixed the MY_STUFF variable problem for projects.  (I didn't feel
> like going through the effort of repackaging everything for fixing the
> CHANGELOG.)
> 
> Of particular interest to me is the number of people who don't have the
> tempnam() function.  (Already asked about zlib and didn't hear anyone
> complain about making it required.)
> 
> Dennis Payne
> dulsi@identicalsoftware.com

looks like it's here on SCO Open Server 5.0.5
does this definition look alright ?

----snip "man tempnam"----
  tmpnam, tempnam -- create a name for a temporary file

  tmpnam- creates a filename using the path-prefix

  tempnam- creates a filename in a named directory

  Syntax
  ======

  cc ... -lc

  #include <stdio.h>

  char *tmpnam(char *s);

  char *tempnam(const char *dir, const char *pfx);

----end snip----

...oh what the hell. here's the rest of it...

----resume snip----
  Description
  ===========

  These functions generate filenames that are not the same as name of an
  existing file.

  The tmpnam function always generates a filename using the path-prefix
  defined as P_tmpdir in the <stdio.h> header file. The generated filename
is
  different each time that tmpnam is called from the same process, up to
  TMP_MAX times. If s is NULL, tmpnam leaves its result in an internal
static
  area and returns a pointer to that area. The next call to tmpnam destroys
  the contents of the area. If s is not NULL, it is assumed to be the
address
  of an array of at least L_tmpnam bytes, where L_tmpnam is a constant
  defined in <stdio.h>; tmpnam places its result in that array and returns
  s.

  tempnam allows choosing a directory. The argument dir points to the name
of
  the directory in which the file is to be created. If dir is NULL or points
  to a string that is not a name for an appropriate directory, the
  path-prefix defined as P_tmpdir in the <stdio.h> header file is used. If
  that directory is not accessible, \/tmp is used as a last resort. This
  entire sequence can be up-staged by providing an environment variable
  TMPDIR in the user's environment, whose value is the name of the desired
  temporary-file directory.

  Many applications prefer their temporary files to have certain favorite
  initial letter sequences in their names. Use the pfx argument for this.
  This argument may be NULL or point to a string of up to five characters to
  be used as the first few characters of the temporary-filename.

  Return value
  ============

  tempnam uses malloc(S) to get space for the constructed filename and
returns
  a pointer to this area. Thus, any pointer value returned from tempnam may
  serve as an argument to free (see malloc(S)).

  If tempnam cannot return the expected result for any reason, i.e.,
malloc(S)
  failed, or none of the above mentioned attempts to find an appropriate
  directory was successful, a NULL pointer is returned.

  Diagnostics
  ===========

  The tempnam function will fail if:

  [ENOMEM]
          Insufficient storage space is available.

  Notes
  =====

  These functions generate a different filename each time they are called.

  Files created using these functions and either fopen(S) or creat(S) are
  temporary only in the sense that they reside in a directory intended for
  temporary use, and their names are unique. It is the user's responsibility
  to use unlink(S) to remove the file when its use is ended.

  If called more than 17,576 times in a single process, these functions
  recycle previously used names.

  Between the time a filename is created and the file is opened, it is
  possible for some other process to create a file with the same name. This
  can never happen if that other process is using these functions or mktemp,
  and the filenames are chosen to render duplication by other means
unlikely.

  See also
  ========

  creat(S), fopen(S), malloc(S), mktemp(S), tmpfile(S), unlink(S)

  Standards conformance
  =====================

  tmpnam is conformant with:

  X/Open Portability Guide, Issue 3, 1989 ;
  ANSI X3.159-1989 Programming Language -- C ;
  IEEE POSIX Std 1003.1-1990 System Application Program Interface (API) [C
  Language] (ISO/IEC 9945-1) ;
  and NIST FIPS 151-1 .

  31 January 1995


-- 
Brian K. White                   http://www.squonk.net/users/linut
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani