![]() | This redirect does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||
|
![]() | The contents of the Header file page were merged into include directive on 19 February 2014. For the contribution history and old versions of the merged article please see its history. |
Headline to thread was missing. I invented an appropriate one. --
Netizen (
talk) 21:34, 29 November 2008 (UTC)
Keeping header file separate seems appropriate.
Akihabara 14:53, 11 July 2005 (UTC)
I think big chunks of this must be a copyvio. Look at this sentence: "Please note that the code segments provided above are in no way the best way to do the projects." Whenever this big slab was inserted, that edit should be reverted. 128.250.37.103 06:46, 11 August 2006 (UTC)
"interfaces in Java are analogous to C header files" seems suspect to me. The two are surely quite different ideas? —Preceding unsigned comment added by 193.113.57.163 ( talk • contribs)
My reversion:
Reasons I think the latter is better:
-- Quuxplusone 03:30, 11 June 2007 (UTC)
Oh, well, if you want to rebut some of my points, I'll make a longer list. :) You say "compiler directive" is not accurate, but you write "intended to be processed by a compiler when another source file is compiled", which implies that compilers are being used here. The first sentence of the article is unnecessarily densely worded. The one-sentence paragraphs on which I did not previously comment also contain grammatical errors, which your reversion re-introduced. I disagree that header files are used "to hold automatically generated code", although included non-header files occasionally are. Please do not blindly revert changes; take a look at what's written and see if you can improve it, or use some of its improvements in your own revision.
Have a nice day! -- Quuxplusone 17:46, 11 June 2007 (UTC)
Nice! This article sure helped me alot in understanding how header files works in c++. I wish to thank the editors alot! Solved a 2h headache.
213.112.109.129 11:48, 21 July 2007 (UTC)
How do you display the contents of a header file using a c++ program??
Curieous 17:46, 08 Feb 2008 (UTC)
The page says that newer languages do no need header files because of a special naming scheme. What kind of special naming scheme is it? Java one-file-per-class? In C# I do not need to use any special naming scheme, it just works when I write class A{ public int f(){return 0;}} in any source file. It does not "restrict file-naming freedom" 217.75.59.233 ( talk) 13:32, 19 August 2009 (UTC)
The following sentence in this article is written presumptively: "This is to keep the interface in the header separate from the implementation." As a first-time reader of this topic, I'm immediately wondering, "What interface?" I come here to try to understand what a header file is, and this sentence suddenly throws at me that there is some interface within headers. What? In all headers? Are headers something that contain "interfaces"? If so, what the hell is meant by an interface? If headers always or usually have "interfaces" in them, then shouldn't the article first state this and immediately explain what an "interface" is? That wasn't meant to be (too) harsh, but contributors should check their own edits for such levels of presumption, and do so as if what they have written were being read by someone unfamiliar with the encompassing subject. — Preceding unsigned comment added by 109.145.82.159 ( talk) 08:42, 19 August 2011 (UTC)
The following sentence in this article is written assumptively: "This is to keep the interface in the header separate from the implementation." As a first-time reader of this topic, I'm immediately wondering, "What interface?" I come here to try to understand what a header file is, and this sentence suddenly throws at me that there is some interface within headers. What? In all headers? Are headers something that contain "interfaces"? If so, what the hell is meant by an interface? If headers always or usually have "interfaces" in them, then shouldn't the article first state this and immediately explain what an "interface" is? That wasn't meant to be (too) harsh, but contributors should check their own edits for such levels of presumption, and do so as if what they have written were being read by someone unfamiliar with the encompassing subject. — Preceding unsigned comment added by 109.145.82.159 ( talk) 08:43, 19 August 2011 (UTC)
Can somebody please provide a live link to this reference http://archive.gamedev.net/reference/programming/features/orgfiles/page2.asp .This link is dead. Jobin ( talk) 12:22, 10 September 2011 (UTC)
![]() | This redirect does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||
|
![]() | The contents of the Header file page were merged into include directive on 19 February 2014. For the contribution history and old versions of the merged article please see its history. |
Headline to thread was missing. I invented an appropriate one. --
Netizen (
talk) 21:34, 29 November 2008 (UTC)
Keeping header file separate seems appropriate.
Akihabara 14:53, 11 July 2005 (UTC)
I think big chunks of this must be a copyvio. Look at this sentence: "Please note that the code segments provided above are in no way the best way to do the projects." Whenever this big slab was inserted, that edit should be reverted. 128.250.37.103 06:46, 11 August 2006 (UTC)
"interfaces in Java are analogous to C header files" seems suspect to me. The two are surely quite different ideas? —Preceding unsigned comment added by 193.113.57.163 ( talk • contribs)
My reversion:
Reasons I think the latter is better:
-- Quuxplusone 03:30, 11 June 2007 (UTC)
Oh, well, if you want to rebut some of my points, I'll make a longer list. :) You say "compiler directive" is not accurate, but you write "intended to be processed by a compiler when another source file is compiled", which implies that compilers are being used here. The first sentence of the article is unnecessarily densely worded. The one-sentence paragraphs on which I did not previously comment also contain grammatical errors, which your reversion re-introduced. I disagree that header files are used "to hold automatically generated code", although included non-header files occasionally are. Please do not blindly revert changes; take a look at what's written and see if you can improve it, or use some of its improvements in your own revision.
Have a nice day! -- Quuxplusone 17:46, 11 June 2007 (UTC)
Nice! This article sure helped me alot in understanding how header files works in c++. I wish to thank the editors alot! Solved a 2h headache.
213.112.109.129 11:48, 21 July 2007 (UTC)
How do you display the contents of a header file using a c++ program??
Curieous 17:46, 08 Feb 2008 (UTC)
The page says that newer languages do no need header files because of a special naming scheme. What kind of special naming scheme is it? Java one-file-per-class? In C# I do not need to use any special naming scheme, it just works when I write class A{ public int f(){return 0;}} in any source file. It does not "restrict file-naming freedom" 217.75.59.233 ( talk) 13:32, 19 August 2009 (UTC)
The following sentence in this article is written presumptively: "This is to keep the interface in the header separate from the implementation." As a first-time reader of this topic, I'm immediately wondering, "What interface?" I come here to try to understand what a header file is, and this sentence suddenly throws at me that there is some interface within headers. What? In all headers? Are headers something that contain "interfaces"? If so, what the hell is meant by an interface? If headers always or usually have "interfaces" in them, then shouldn't the article first state this and immediately explain what an "interface" is? That wasn't meant to be (too) harsh, but contributors should check their own edits for such levels of presumption, and do so as if what they have written were being read by someone unfamiliar with the encompassing subject. — Preceding unsigned comment added by 109.145.82.159 ( talk) 08:42, 19 August 2011 (UTC)
The following sentence in this article is written assumptively: "This is to keep the interface in the header separate from the implementation." As a first-time reader of this topic, I'm immediately wondering, "What interface?" I come here to try to understand what a header file is, and this sentence suddenly throws at me that there is some interface within headers. What? In all headers? Are headers something that contain "interfaces"? If so, what the hell is meant by an interface? If headers always or usually have "interfaces" in them, then shouldn't the article first state this and immediately explain what an "interface" is? That wasn't meant to be (too) harsh, but contributors should check their own edits for such levels of presumption, and do so as if what they have written were being read by someone unfamiliar with the encompassing subject. — Preceding unsigned comment added by 109.145.82.159 ( talk) 08:43, 19 August 2011 (UTC)
Can somebody please provide a live link to this reference http://archive.gamedev.net/reference/programming/features/orgfiles/page2.asp .This link is dead. Jobin ( talk) 12:22, 10 September 2011 (UTC)