Problem to understand header file

[Pramod]

Hello to all of you.

I was seeing a header file. Before many function they wrote _cdecl,
_stdcall, _pascal, _fastcall and _attribute_ ..Please explain me
meaning of this.

Thank you

 

[Alf P. Steinbach]

* Pramod:

Hello to all of you.

I was seeing a header file. Before many function they wrote _cdecl,
_stdcall, _pascal, _fastcall and _attribute_ ..Please explain me
meaning of this.

They are compiler-specific language extensions.

Thus, off-topic here (in general).

Please read the manual for your compiler.


Cheers, & hth.,

- Alf

 

[Neelesh Bodas]

Hello to all of you.

I was seeing a header file. Before many function they wrote _cdecl,
_stdcall, _pascal, _fastcall and _attribute_ ..Please explain me
meaning of this.

Thank you

"calling conventions".
http://en.wikipedia.org/wiki/X86_calling_conventions

 

[Pramod]

* Pramod:



They are compiler-specific language extensions.

Thus, off-topic here (in general).

Please read the manual for your compiler.

Cheers, & hth.,

- Alf

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Thanks....but if you know any thing about this topic then please
explain me. can we use all of this in our program.

 

[Pramod]

"calling conventions".http://en.wikipedia.org/wiki/X86_calling_conventions

thanks really its a good link. if you have any document or information
about topic then please share it with me.

 

[ravinder thakur]

thanks really its a good link. if you have any document or information
about topic then please share it with me.

see this. just found by googling "calling conventions"

http://www.codeproject.com/cpp/calling_conventions_demystified.asp

 

[James Kanze]

I was seeing a header file. Before many function they wrote _cdecl,
_stdcall, _pascal, _fastcall and _attribute_ ..Please explain me
meaning of this.

It means that the header is not C++. It might be some
implementation specific extensions (the leading _ suggests
this, althought two __ would be more reasonable), or it
might some completely different language, but it's not C++.

 

[Pramod]

It means that the header is not C++. It might be some
implementation specific extensions (the leading _ suggests
this, althought two __ would be more reasonable), or it
might some completely different language, but it's not C++.

--
James Kanze (GABI Software) mailto:[email protected]
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

Ya you are right James. Its not a C++ file its a C header file. Please
explain me it.

 

[Ian Collins]

*please* don't quote signatures

Ya you are right James. Its not a C++ file its a C header file. Please
explain me it.

It isn't standard C either, it's a specific compiler's dialect. You'll
have to ask in a group dedicated to your compiler or platform.

 

[James Kanze]

It means that the header is not C++. It might be some
implementation specific extensions (the leading _ suggests
this, althought two __ would be more reasonable), or it
might some completely different language, but it's not C++.

[/QUOTE]

Ya you are right James. Its not a C++ file its a C header file. Please
explain me it.

It's not C either. As I said, the leading _ suggests some
implementation specific extensions, although the usual
convention for such things is a double __: things like _stdcall,
etc., are perfectly legal identifiers other than at namespace
scope (but they aren't a good idea, because too many systems to
capture them for other things).