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

[j_del_strother@hotmail.com (Jon)]

Vinzent Hoefler <JeLlyFish.software@gmx.net> wrote in message news:<3dc6e966_1@news.bluewin.ch>...
> j_del_strother@hotmail.com (Jon) wrote:
> 
> >Which leads on to my next question...
> >Can you call a function & ignore its return value?  I'm using a lot of
> >Win32 calls, all of which are written as functions rather than
> >procedures, and I'm getting a huge mess of useless temporary variables
> >just to allow me to call the functions.
> 
> Are you *sure*, you won't have to check the function result?
> 

In some cases, absolutely.  For example, flipping a bitmap to the DC
will return the old bitmap that was originally stored there.  I then
have to create a useless temporary variable for it...

> Perhaps you could use a declare block around the "function" call with
> a local variable to store the result. The optimizer should be easily
> able to remove this reference.
> 

Sure, but it gets very messy when you're calling several dozen C
functions.



Thanks for the help guys, I'll look into the pragma stuff.