*.hpp files

[T. F.]

A short question:

What exactly are *.hpp files? I mean how are they different from other
header files?

[tom_usenet]

Re: *.hpp files

On Thu, 04 Sep 2003 19:09:55 +0200, T. F. <reptile2k@gmx. net> wrote:
[color=blue]
>A short question:
>
>What exactly are *.hpp files? I mean how are they different from other
>header files?[/color]

There is no fixed extension for header files. You can use .h, .hpp,
H, .hxx, or whatever you fancy (".C++ header", say) that your
platform can handle. Standard headers have no extension, and the
standard C headers have .h extensions, but apart from that it's up to
you.

Tom

[red floyd]

Re: *.hpp files

T. F. wrote:[color=blue]
> A short question:
>
> What exactly are *.hpp files? I mean how are they different from other
> header files?[/color]

They're some peoples' way of indicating that a header file is for C++ (much
as some people use .cpp for C++ source).

[Gianni Mariani]

Re: *.hpp files

tom_usenet wrote:[color=blue]
> On Thu, 04 Sep 2003 19:09:55 +0200, T. F. <reptile2k@gmx. net> wrote:
>
>[color=green]
>>A short question:
>>
>>What exactly are *.hpp files? I mean how are they different from other
>>header files?[/color]
>
>
> There is no fixed extension for header files. You can use .h, .hpp,
> H, .hxx, or whatever you fancy (".C++ header", say) that your
> platform can handle. Standard headers have no extension, and the
> standard C headers have .h extensions, but apart from that it's up to
> you.
>[/color]

Suggestion:

Unless you really really need to, I suggest that you don't invent new
suffixes for header files. This is not exactly somthing that needs any
creativity. Besides, some tools, (like ones I have written) attempt to
identify headers by the file suffix and would need tweaking to work for
new suffixes.

[Jeremy Cowles]

Re: *.hpp files

> creativity. Besides, some tools, (like ones I have written) attempt to[color=blue]
> identify headers by the file suffix and would need tweaking to work for
> new suffixes.[/color]

That's a flaw in your app, you are using rules that don't really exist. Your
app should take into account that header files can be of any extention (or
lack thereof) or name.

[Jeremy Cowles]

Re: *.hpp files

> >>creativity. Besides, some tools, (like ones I have written) attempt to[color=blue][color=green][color=darkred]
> >>identify headers by the file suffix and would need tweaking to work for
> >>new suffixes.[/color]
> >
> >
> > That's a flaw in your app, you are using rules that don't really exist.[/color][/color]
Your[color=blue][color=green]
> > app should take into account that header files can be of any extention[/color][/color]
(or[color=blue][color=green]
> > lack thereof) or name.[/color]
>
> So, if you want to invent new suffixes, go right ahead, just expect to
> be wading through a whole bunch of tools trying to figure out how to
> configure them to accept new suffixes.[/color]

This is a *standard* programmer response, "it's not my apps fault, it's the
users fault", well that's not how it works, if you don't implement something
based on previously established rules, it means that your program is flawed,
not the user who is just following the rules.

Just think if the developer of your compiler just said, hey, the "New"
keyword is stupid, if you use it, thats your fault, not my compiler, and
never documented this fact.

Good software has no room for laziness and inflated egos.

[Thomas Matthews]

Re: *.hpp files

T. F. wrote:
[color=blue]
> A short question:
>
> What exactly are *.hpp files? I mean how are they different from other
> header files?[/color]

I use the ".hpp" extension for C++ header files, ".cpp" for sources.
I use ".h" for C language files and ".c" for sources.
The Borland Compiler wishes everybody would use ".h" for header files.

Header files can have any filename, that is valid with your operating
system. The ".hpp" is just a common convention.

--
Thomas Matthews

C++ newsgroup welcome message:

http://www.slack.net/~shiva/welcome.txt

C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.l earn.c-c++ faq:

http://www.raos.demon.uk/acllc-c++/faq.html

Other sites:
http://www.josuttis.com -- C++ STL Library book

[Jeremy Cowles]

Re: *.hpp files

I know that last post was mildly inflamitory, sorry about that. I just have
strong feelings when it comes to this type of thing.


"Jeremy Cowles" <jeremy.cowle s[nosp@m]asifl.com> wrote in message
news:Ij16b.1037 1$875.428244@tw ister.tampabay. rr.com...[color=blue][color=green][color=darkred]
> > >>creativity. Besides, some tools, (like ones I have written) attempt[/color][/color][/color]
to[color=blue][color=green][color=darkred]
> > >>identify headers by the file suffix and would need tweaking to work[/color][/color][/color]
for[color=blue][color=green][color=darkred]
> > >>new suffixes.
> > >
> > >
> > > That's a flaw in your app, you are using rules that don't really[/color][/color][/color]
exist.[color=blue]
> Your[color=green][color=darkred]
> > > app should take into account that header files can be of any extention[/color][/color]
> (or[color=green][color=darkred]
> > > lack thereof) or name.[/color]
> >
> > So, if you want to invent new suffixes, go right ahead, just expect to
> > be wading through a whole bunch of tools trying to figure out how to
> > configure them to accept new suffixes.[/color]
>
> This is a *standard* programmer response, "it's not my apps fault, it's[/color]
the[color=blue]
> users fault", well that's not how it works, if you don't implement[/color]
something[color=blue]
> based on previously established rules, it means that your program is[/color]
flawed,[color=blue]
> not the user who is just following the rules.
>
> Just think if the developer of your compiler just said, hey, the "New"
> keyword is stupid, if you use it, thats your fault, not my compiler, and
> never documented this fact.
>
> Good software has no room for laziness and inflated egos.
>
>
>[/color]

[jeffc]

Re: *.hpp files


"Gianni Mariani" <gi2nospam@mari ani.ws> wrote in message
news:bj7st6$o6g @dispatch.conce ntric.net...[color=blue]
>
> Unless you really really need to, I suggest that you don't invent new
> suffixes for header files. This is not exactly somthing that needs any
> creativity.[/color]

I thought you like to think outside the box? I thought you used whatever
means necessary to solve the problem at hand? Now you are conforming?

[llewelly]

Re: *.hpp files

"jeffc" <nobody@nowhere .com> writes:
[color=blue]
> "Gianni Mariani" <gi2nospam@mari ani.ws> wrote in message
> news:bj7st6$o6g @dispatch.conce ntric.net...[color=green]
>>
>> Unless you really really need to, I suggest that you don't invent new
>> suffixes for header files. This is not exactly somthing that needs any
>> creativity.[/color]
>
> I thought you like to think outside the box? I thought you used whatever
> means necessary to solve the problem at hand? Now you are
> conforming?[/color]

Yes. Thinking out of the box is good for you. I pull some bits out of
/dev/random to use as a header file extension. It is hard to
remember the suffixes of some of my headers, but I am sure the
habit keeps me on my toes and improves my mental agilty. It is the
thinking man's equivalent to laying on the ground and rolling to
work, as opposed to driving or taking the subway.