Keith said:
Keith:
If I use Borland's C to compile each of my modules (say commonly,
several dozen major source .prg files) of my business application, and in
the logging sequence of the build there are no errors in that compilation,
then I *must* be using C ?
So what? I will not try to copy Dan Pop's style, but you might benefit
from reading some of his posts. Your business application is not in
itself C. If someone using your application were to post questions here
about how to use it, based on the completely silly idea that because it
is written in C it _is_ C, he would obviously be in the wrong place.
Or are you saying that Borland's C compiles all sorts of things that are
*not* C ??
Besides the obvious that BCC also compiles things written in C++, a
language that is not C, you suffer from a confusion which, honestly, I
can't imagine any intelligent person having. Things written in C are
not C. There is a vast array of programming languages, editors, among
many other things, that are written in C and are not C.
Someone who has problems writing C code in implementing a BASIC
interpreter may have C questions. Someone having problems writing a
program for that BASIC does _not_ have a C question.
See what? That you are hopelessly confused?
But may you may wish to call it 'Hi C' for High-level C ??
No, it's not C at all. Get a clue.