Re: Automatically generate variables

On Tue, 20 Feb 2007 02:27:36 GMT, in comp.lang.c , Yevgen Muntyan
<muntyan.removethis@xxxxxxxx> wrote:

Mark McIntyre wrote:
On Mon, 19 Feb 2007 06:30:00 GMT, in comp.lang.c , Yevgen Muntyan

And? Is this program C or not?

It is _potentially_ a C programme. However since we have no idea at

Yes you do. That's the point.

No, you don't. That is indeed the point. If stdlib.h were included,
you would know it was a C programme, since stdlib.h is a standard
header. if foobar.h is included, you have no idea at all unless you
have the contents of foobar.h

You know pretty well the program was
a C program but you wanted to tell couple nice words to Jacob Navia,

You think I have a vendetta against Jacob. You're wrong. I do have an
objection to people posting gratuitously offtopic stuff here tho.
Windows-specific code is offtopic.

so you did "beep beep not C". Bull***.

Horsefeathers.

The point CBF was making here is that had the user supplied the
contents of windows.h, we oculd have been certain whether it was C or
not. As it is, it could be packed with assembler, platform-specific
memory access which violates C standards, etc etc etc.

Well, the point was hidden pretty well.

Possibly. See my sig.

say *not C* if you do *not* know that? I simply assume that

We know what "assume" makes out of you and me.

header is indeed the famous windows.h thing, windows C api,
for C programs. You?

I have several headers called Windows.h, two of which deal with the
win32API, but for different compilers and with slightly different
contents. Both of them give rise to compilation errors during
compilation in ISO C mode. A third is for PalmOS as far as I remember
(I haven't used it in a while). A few years ago, I worked for a
company that gathered together all their GUI control declarations into
a file called - you guess.

--
Mark McIntyre

"I hope, some day, to learn to read.
It seems to be even harder than writing."
--Richard Heathfield
.