Re: Automatically generate variables

CBFalconer wrote:
Yevgen Muntyan wrote:
... snip ...
It does, indeed. Point is that calling conventions, preprocessor
magic, syntax are all the same. If your program is

#include <windows.h>
int main (void)
{
return 0;
}

then it's a C program. If your program is

No it isn't. If it had #include "windows.h" it would be.

I'm afraid I can't understand this.

There is
no such header in standard C, but the user is allowed to create all
the headers he wishes elsewhere. All he has to do is provide them.

And? Is this program C or not? If not, what is it (just curious
what ridiculous things people can invent instead of using standard
"strictly conforming" term). And please don't tell "this is not standard
C", I didn't say that. I am saying "it is a C program".

Yevgen
.

Relevant Pages

  • Re: Compiler Error
    ... is preferred to "void main" ... I'd have used a stronger expression than that. ... actually requires int in almost all situations in which the Standard ...
    (comp.lang.c)
  • Re: LNK2005...
    ... every file that includes your header is also ... extern int myvarible; ... > afx_msg void OnRecordEnd(); ... > DWORD dwInstance, ...
    (microsoft.public.windowsce.embedded.vc)
  • [PATCH 3/3] eCryptfs: Encrypted passthrough
    ... whether the metadata is actually in the header or in the extended ... -static void ... size_t size, int flags); ...
    (Linux-Kernel)
  • Re: Question about pointers?
    ... > with the exception of the void fileexistcheckthat is OS ... I hope the rest of it is totally standard. ... > int main ... > void selectfilename(string& filename) ...
    (comp.lang.cpp)
  • Re: Memory allocation for an initialized character pointer;
    ... where does the Standard explicitly mention void ... the Standard does not imply by that text that void mainis ... any more than the Standard implies by the same text that struct ... Neither does it imply that int mainis correct, because, as you ...
    (comp.lang.c)