🚀 go-pugleaf

arno@yaps.rhein.de (Arno Eigenwillig) wrote:

>In article <48iptn$b1q@macondo.dmu.ac.uk>, Richard Perrott writes:
>
>> 1. strncpy() in string.h does not put a '\0' at the end of the destination 
>> string if the source string is the same length as the copy length.
>
>It is defined that way by ANSI.
>
>> 2. the #defines in ctype.h e.g. toupper() cause problems since the term is 
>> used more than once, a problem with *s++ terms.
>
>Of the ANSI functions, only tolower() and toupper() are concerned.
>The workaround is to #undef them or parenthesize the function names.
>I wonder, though, what the ANSI-C experts think of this. (Hence
>x-posting and f'up2.)

The standard requires that anything defined as a function in the
standard (this includes toupper() and tolower()) behave like a
function.  In particular (ISO 7.1.7):

	Any invocation of a library function that is implemented as a macro 
	shall expand to code that evaluates each of its argtuments exactly 
	once, fully protected by parentheses wehre necessary, so it is 
	generally safe to use arbitrary expressions as arguments.

Michael M Rubenstein