🚀 go-pugleaf

In article <4ii35g$nno@solutions.solon.com>,
billy@cast.msstate.edu (Billy Chambless) wrote:

>True story: we have a student worker right now who was hired partly on
>the basis of his having had a class or two in C. It turns out that what
>he was taught in his "C" calss was actually Borland C++, that bastard,
>mongrel language-from-hell. He's talented, but it took him a while to
>learn to create code that worked under an actual C compiler.

While I understand your point, the current Borland compilers have both
a C mode and a C++ mode.  It is a very good C compiler in C mode in my
opinion, but you have to know the line between Standard C and
implementation extensions.  

I have noticed that many people aren't aware of whether they are
compiling in C or C++ mode, a shame.  Besides mixing "almost C" with
// comments, they typically include compiler- and operating
system-dependent header files without good reason.

Thad