>>>>> Paul Kranenburg writes:

 >> |     mktemp("/tmp/temp.XXXX");
 > You are passing a read-only constant, where mktemp() expects to able
 > to modify the trailing XXXXs in place to return the result.

Wow, thanks for the quick reply.

One more question, just out of curiosity: Obviously gcc places the
string in the code segment, which is per default 'const'. mktemp() on
the other hand is not defined to treat the buffer as const, for
obvious reasons, so shouldn't gcc complain?

	-peter