24 Apr
1998
24 Apr
'98
10:38 a.m.
On Fri, 24 Apr 1998, Captain Napalm wrote:
It was thus said that the Great Pete Turnbull once
stated:
The ANSI standard is not completely silent on the matter, but does not
define the behavior.
According to section 4.1.6 Use of Library Functions:
"Each of the following statements applies unless explicitly stated
otherwise in the detailed descriptions that follow. If an argument
to a function has an invalid value (such as a value outside of the
domain of the function, or a pointer outside the address space of
the program or a null pointer), the behavior is undefined."
So says ANSI X3.159-1989. So shall it be.
--pec (who likes reading the standard a little too much)
--------------------------------------------------------------------------
The Antique Computer Collection: http://www.wco.com/~pcoad/machines.html
On Apr 24, 1:35, Captain Napalm wrote:
Well, I've tried it across four platforms and five compilers (Linux/GCC,
Solaris/native and GCC, AIX/native and HPUX/native) and three of the five
core dumped.
I checked the standard and it doesn't say what it should do in case one of
the parameters is NULL, so I assume this is an implementation detail and the
safest thing to do is assume you can't strcpy() a NULL pointer (which I do
anyway).
-spc (Considers that a feature, not a bug) Well, I snagged a copy of it, compiled it,
found a bug, and fixed it.
strcpy() (at least on my compiler) will crash if any of the parameters
are NULL pointers,
That's a compiler (or library, actually) bug. You should be able to copy a
null string.