Re: [Wvware-devel] tmpnam

[Bob F. <bfr...@si...>]

This is indeed a dreadful warning from the compiler.  Indeed the
compiler should be fixed. :-)

From the Solaris mkstemp() manual page

"    For portability  with  X/Open  standards  prior  to  XPG4v2,
     tmpfile(3S) is preferred over this function."

The functions are not really equivalent.  They require a design change
to the program.

Bob

On Tue, 12 Feb 2002, John Harrison wrote:

> Hi,
> 
> I'm getting this when I make wv-0.7.1 :
> 
> ./stylesheet.c: In function `wvGetSTD':
> ./stylesheet.c:189: warning: assignment from incompatible pointer type
> ./libwv.a(generic.o): In function `wvTempName':
> /usr/src/wv-0.7.1/./generic.c:92: the use of `tmpnam' is dangerous, better use `mkstemp'
> ./libwv.a(utility.o): In function `TemporaryFilename':
> /usr/src/wv-0.7.1/magick/./utility.c:126: the use of `tempnam' is dangerous, better use `mkstemp'
> ./libwv.a(generic.o): In function `wvTempName':
> /usr/src/wv-0.7.1/./generic.c:92: the use of `tmpnam' is dangerous, better use `mkstemp'
> ./libwv.a(generic.o): In function `wvTempName':
> /usr/src/wv-0.7.1/./generic.c:92: the use of `tmpnam' is dangerous, better use `mkstemp'
> ./libwv.a(generic.o): In function `wvTempName':
> /usr/src/wv-0.7.1/./generic.c:92: the use of `tmpnam' is dangerous, better use `mkstemp'
> 
> Should this be fixed ?
> 
> Kind regards,
> 
> John
> 
> 
> _______________________________________________
> Wvware-devel mailing list
> Wvw...@li...
> https://lists.sourceforge.net/lists/listinfo/wvware-devel
> 

======================================
Bob Friesenhahn
bfr...@si...
http://www.simplesystems.org/users/bfriesen