Re: Compiler error: 'Expect procedure name in procedure call'

[Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>]

Jim Rogers <jimmaureenrogers@worldnet.att.net> writes:

> You are actually calling C functions. It is still a bad idea to
> ignore a return value. The return value is your only indication of an
> error from a C function. Ignoring errors is a BAD idea.

For most C functions, I agree with this. However, for the specific
case of Win32 C functions, many have a return value which is _defined_
to be "TRUE", and many others have no documentation on what the return
value might be.  This is a side effect of the C compilers letting you
ignore return values; the Win32 authors apparently said something like
"Well, this return value is pretty meaningless, but people can always
ignore it, and we have a coding standard that says 'return a value'"
:). 

So in some cases, if you have documentation and testing to back it up,
you _should_ ignore return values.

-- 
-- Stephe