difference in header files

[Pradyut]

what's the difference between a .h and a .hpp file
Also please tell me something about .rh files
--
Pradyut
http://pradyut.tk
http://groups.yahoo.com/group/d_dom/
http://groups-beta.google.com/group/oop_programming
India

[Walter Roberson]

In article <42************ ***********@aut hen.white.readf reenews.net>,
Pradyut <pr******@gmail .com> wrote:

what's the difference between a .h and a .hpp file
C doesn't promise that a .hpp file can be #include'd -- unique
mappings are promised only for (up to) 6-characters followed by a
single character.
Also please tell me something about .rh files

As per above, C doesn't promise that .rh files are usable either.
Perhaps you are thinking of some other programming language, such
as C++?
--
Ceci, ce n'est pas une idée.

[Kulka]

Pieknego dnia Wed, 10 Aug 2005 01:22:17 +0530,
osobnik Pradyut napisa³(a):

what's the difference between a .h and a .hpp file

..hpp are header files for c++, while h for c

--
\x6b\x75\x6c\x6 b\x61

[E. Robert Tisdale]

Pradyut wrote:

what's the difference between a *.h and a *.hpp file
These file extensions are arbitrary but customary.
You can include files with *any* file name extension or none at all.
Also please tell me something about .rh files

Which is what appears to have been done here.

The *.h extension was added to [UNIX] file names
to suggest that the file was a C *header* file
instead of a C *source* file.
The *.hpp file name extension is sometimes used
to distinguish C++ header files from C header files.

A header file is a file that is included near the top (head)
of a translation unit (source file) or another header file.
It may contain *any* valid C code
but header files are commonly used
to introduce a module interface into a translation unit.
The module interface contains C preprocessor macro definitions,
type definitions, constant definitions,
function and variable declarations
that do not by themselves require the compiler to emit code
or reserve space for objects.

[Mark McIntyre]

On Wed, 10 Aug 2005 01:22:17 +0530, in comp.lang.c , "Pradyut"
<pr******@gmail .com> wrote:

what's the difference between a .h and a .hpp file
this would be something specific to your implementation or company
style. C doesn't place any particular requirements on the file
extensions - remember that its only MSDOS and its children that think
the extension is an indication of the file's format, most other OSen
find it more useful to store that info elsewhere...

<ot>
some people like to use hpp for C++ includes and h for C ones.
</ot>
Also please tell me something about .rh files

Something else system-specific. Possibly resource includes? Ask in a
newsgroup specialising in your compiler.
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Walter Roberson]

In article <dd**********@n ntp1.jpl.nasa.g ov>,
E. Robert Tisdale <E.************ **@jpl.nasa.gov > wrote:

These file extensions are arbitrary but customary.
You can include files with *any* file name extension or none at all.

C89 doesn't promise that it will be able to uniquely locate files
whose extension is more than 1 character long. (C89 doesn't want to
impose any filesystem semantics onto freestanding implementations .)
--
This signature intentionally left... Oh, darn!

[Robert Gamble]

Walter Roberson wrote:

In article <dd**********@n ntp1.jpl.nasa.g ov>,
E. Robert Tisdale <E.************ **@jpl.nasa.gov > wrote:

These file extensions are arbitrary but customary.
You can include files with *any* file name extension or none at all.

C89 doesn't promise that it will be able to uniquely locate files
whose extension is more than 1 character long.

Yup, the same stands for C99 as well. Not only that, the 1 character
must be a *letter* to qualify for this this guarantee. Additionally,
since the implementation may ignore the case of filenames in #include
directives, it need not differentiate between header.h and header.H (or
HEADER.H for that matter).

Robert Gamble

[Jack Klein]

On Tue, 9 Aug 2005 19:58:39 +0000 (UTC), ro******@ibd.nr c-cnrc.gc.ca
(Walter Roberson) wrote in comp.lang.c:

In article <42************ ***********@aut hen.white.readf reenews.net>,
Pradyut <pr******@gmail .com> wrote:

what's the difference between a .h and a .hpp file

C doesn't promise that a .hpp file can be #include'd -- unique
mappings are promised only for (up to) 6-characters followed by a
single character.

Note that this is, and has been since 1999:

"The implementation shall provide unique mappings for sequences
consisting of one or more letters or digits (as defined in 5.2.1)
followed by a period (.) and a single letter. The first character
shall be a letter. The implementation may ignore the distinctions of
alphabetical case and restrict the mapping to eight significant
characters before the period."

So it now 8 characters, and the standard now includes three standard
headers that have more than six significant characters before the
period: <complex.h>, <stdbool.h>, and <inttypes.h>

Other than the standard headers, C places no restrictions at all on
the contents of <h_char_sequenc e> or "q_char_sequenc e" in a #include
directive. If between them the implementation and underlying platform
map them into a file "that can be processed by the application", it
causes the replacement of the directive by the entire contents of the
file.

If the sequence does not match a standard header and does not map to
the name of a file that can be processed by the application, it is a
constraint error and a diagnostic is required.

Also please tell me something about .rh files

As per above, C doesn't promise that .rh files are usable either.
Perhaps you are thinking of some other programming language, such
as C++?

I don't really see what C++ has to do with it.

Even under MS-DOS, in fact even under CP/M 80, I could expect:

#include "filename.r h"

....to do what I wanted, assuming there was a file named filename.rh in
the implementation-defined search path. Although AFAIK there was
never a C90 conforming implementation for CP/M 80.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.l earn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

[Jack Klein]

On Tue, 9 Aug 2005 21:59:32 +0000 (UTC), ro******@ibd.nr c-cnrc.gc.ca
(Walter Roberson) wrote in comp.lang.c:

In article <dd**********@n ntp1.jpl.nasa.g ov>,
E. Robert Tisdale <E.************ **@jpl.nasa.gov > wrote:

These file extensions are arbitrary but customary.
You can include files with *any* file name extension or none at all.

C89 doesn't promise that it will be able to uniquely locate files
whose extension is more than 1 character long. (C89 doesn't want to
impose any filesystem semantics onto freestanding implementations .)

Where does C89, or any other version, mention an implementation that
runs (as opposed to builds code for) a free-standing environment?

No environment for translators is mentioned at all. The distinction
between hosted and free-standing environments has to do with
execution, not translation.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.l earn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html

[Lawrence Kirby]

On Tue, 09 Aug 2005 21:47:33 -0500, Jack Klein wrote:

On Tue, 9 Aug 2005 21:59:32 +0000 (UTC), ro******@ibd.nr c-cnrc.gc.ca
(Walter Roberson) wrote in comp.lang.c:

In article <dd**********@n ntp1.jpl.nasa.g ov>,
E. Robert Tisdale <E.************ **@jpl.nasa.gov > wrote:

>These file extensions are arbitrary but customary.
>You can include files with *any* file name extension or none at all.

C89 doesn't promise that it will be able to uniquely locate files
whose extension is more than 1 character long. (C89 doesn't want to
impose any filesystem semantics onto freestanding implementations .)

Where does C89, or any other version, mention an implementation that
runs (as opposed to builds code for) a free-standing environment?

No environment for translators is mentioned at all. The distinction
between hosted and free-standing environments has to do with
execution, not translation.

The standard sepcifies hosted and freestanding implementations as well as
execution environments. This is highly relevant to translation, for
example #include <stdio.h> may legitimately fail during translation on a
freestanding implementation.

Lawrence