strcpy wars, jeez! A proposed resolution.

[Justin Chris Vallon]

>"... implementation defined."

Means NON-PORTABLE!  If implementation X does it one way [ie strcpy(s, s+1)
works], and implementation Y does it another way [ie strcpy(s, s+1) does not
work], my program will behave very differently on different systems, but both
strcpy() functions adhere to the ANSI specs.

I cannot expect an ANSI standard which isn't a standard.  Isn't non-portable
code something that ANSI is trying to prevent, not endorse?

-Justin