By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,035 Members | 1,543 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,035 IT Pros & Developers. It's quick & easy.

undef ref wcpp_4_fs_handler When Using Try Catch in Watcom 1.9

P: 3
Hi all I have been using WATCOM C++ for some time quite ok. Now I want to use C++ exception handling.

I can make little Micky Mouse programs work but when I add try and catch to my existing code I get an undefined ref of __wcpp_4_fs_handler__.

I am going spare trying to figure this out.
Sep 2 '10 #1

✓ answered by poitiere

Hi weaknessforcats

Thanks for caring: I didn't post any code because there is too much. Out of 200 c++ files about 55 had the undef.
As you can surmise I have solved it the hardway trying to suss out why some had it and others didn't but each time I thought I had it sussed I implemented the complexity in the Micky Mouse test program. But all was kosher. I made 1 or 2 files clean by removing local objects from methods and initializing in the constructor init list.

But it didn't make sense; I studied c++ by stroustrup (man that cat is a clear thinker (not like these politicians)) and what I was doing was cool.

Eventually it dawned on me that there must be something in my header files causing Watcom to "freak". By process of elimination I traced it to an old legacy cdecl pragma unused but still present in a header.

Share this Question
Share on Google+
2 Replies


weaknessforcats
Expert Mod 5K+
P: 9,197
Maybe you could post a sample of your code illustrating the problem?
Sep 2 '10 #2

P: 3
Hi weaknessforcats

Thanks for caring: I didn't post any code because there is too much. Out of 200 c++ files about 55 had the undef.
As you can surmise I have solved it the hardway trying to suss out why some had it and others didn't but each time I thought I had it sussed I implemented the complexity in the Micky Mouse test program. But all was kosher. I made 1 or 2 files clean by removing local objects from methods and initializing in the constructor init list.

But it didn't make sense; I studied c++ by stroustrup (man that cat is a clear thinker (not like these politicians)) and what I was doing was cool.

Eventually it dawned on me that there must be something in my header files causing Watcom to "freak". By process of elimination I traced it to an old legacy cdecl pragma unused but still present in a header.
Sep 3 '10 #3

Post your reply

Sign in to post your reply or Sign up for a free account.