Re: Compiler keeps giving Fatal Error message

[ Follow Ups ] [ Post Followup ] [ CS1044 Web Discussion Board ] [ FAQ ]

Posted by Amit Agarwal on November 06, 2001 at 20:02:28:

In Reply to: Re: Compiler keeps giving Fatal Error message posted by Simon on January 30, 2001 at 19:35:20:

I had the same problem. I have now figured it out. The program generated a fatal whenever an library was included because -

1. iostream library has calls to eh.h.

2. Now, eh.h checks for system incompatibility error, file extension errors and so on. My program had a .C extension. BUT, the 6.0 updated version (unlike other 6.0 versions I have used), DOES NOT permit to be included with any .C program. If that is done, eh.h will catch it as a fatal error. The solution is, name the files with .CPP extension ONLY. I figured this out by taking a closer look at the eh.h file itself. In fact, a .C file extension will give an error whenever ANY library that calls eh.h is included.

Follow Ups:

Post a Followup

Name:
E-Mail:

Subject:

Comments:
: I had the same problem. I have now figured it out. The program generated a fatal whenever an <iostream> library was included because - : 1. iostream library has calls to eh.h. : 2. Now, eh.h checks for system incompatibility error, file extension errors and so on. My program had a .C extension. BUT, the 6.0 updated version (unlike other 6.0 versions I have used), DOES NOT permit <iostream> to be included with any .C program. If that is done, eh.h will catch it as a fatal error. The solution is, name the files with .CPP extension ONLY. I figured this out by taking a closer look at the eh.h file itself. In fact, a .C file extension will give an error whenever ANY library that calls eh.h is included.

Optional Link URL:
Link Title:
Optional Image URL:

[ Follow Ups ] [ Post Followup ] [ CS1044 Web Discussion Board ] [ FAQ ]