Re: is 'finally' a reserved word in windows CE in a C program?

The eVC4 help has a page called C++ Keywords that lists everything.
__finally is part of structured exception handling (C exceptions), while
finally is part of C++ exception handling. Both are reserved words, when
compiling C++. I think that, if you set the C option to compile your code
as C, not C++, you can reuse finally, although the editor might syntax color
it like it's reserved.

Paul T.

"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
news:eGn0iTeNIHA.2140@xxxxxxxxxxxxxxxxxxxxxxx
I think it's not just for SEH. CE has a __try/__finally construct without
SEH and my bet is that the macro is doing a replacement to use that if SEH
isn't included.

No idea on a global list of reserved words.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com


"Timothy Wojtaszek" <TimothyWojtaszek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C78DC768-5B03-41D9-BE5B-EADA6B522513@xxxxxxxxxxxxxxxx
Could you point me to the documentation for CE that list reserved words.
If
i need to make a project wide replacement for this idiom i would not want
to
repeat this behavior.

Also, it seem this should only be a reserved word when SEH is enabled.
Is
there something one can do to disable SEH? I'm looking into trimming the
include files to something that won't include excpt.h, since it isn't
being
used.

Thanks,
tim

"<ctacke/>" wrote:

Yes, it's a reserved word. It's part of exception handling.
try/catch/finally


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



"Timothy Wojtaszek" <Timothy Wojtaszek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:D21AB4A9-B8F3-441C-8337-4FC3F8DCE468@xxxxxxxxxxxxxxxx
The issue seems to be a problem in the excpt.h header defined for the
windows
CE SDK. I have a c program and it uses a form of labels & gotos to
handle
some error handling. The code follows a java style by using the label
'finally'.

If the excpt.h file is included by some windows header, it will do a
#define finally __finally

This is causing problems for the compiler at this point. Is this
intentional? I can't see any documentation that says to avoid using
'finally' in a c program?









.

Loading