Re: [Cegcc-devel] Problem using ExitProcess

2009-05-18 Thread Johnny Willemsen
Hi, > If ExitProcess is a function without a return value, then > the return statement you write in the example below is not valid. So > the > compile error is justified. > > Or am I missing something ? Bad example code ;-), the return was a left over I shouldn't have added Try to just call ::

Re: [Cegcc-devel] Problem using ExitProcess

2009-05-18 Thread Danny Backx
If ExitProcess is a function without a return value, then the return statement you write in the example below is not valid. So the compile error is justified. Or am I missing something ? Danny On Mon, 2009-05-18 at 10:39 +0200, Johnny Willemsen wrote: > Hi, > > Btw, WinCE ships with Ex

Re: [Cegcc-devel] Problem using ExitProcess

2009-05-18 Thread Johnny Willemsen
Hi, Btw, WinCE ships with ExitProcess, see http://msdn.microsoft.com/en-us/library/ms885217.aspx Johnny > We have a compile problem when trying to use ExitProcess. Using it > without > return works (see the example with value 3), but using it with return > results in a compile error (see 4). I t

[Cegcc-devel] Problem using ExitProcess

2009-05-18 Thread Johnny Willemsen
Hi, We have a compile problem when trying to use ExitProcess. Using it without return works (see the example with value 3), but using it with return results in a compile error (see 4). I think the ExitProcess should be an inline function instead of a define. Johnny #include int main (int argc,