X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE's Long FileName Support?
Date: 3 Apr 2004 10:38:18 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 25
Message-ID: <c4m46q$8nc$3@nets3.rz.RWTH-Aachen.DE>
References: <Eumbc.11333$Tx6 DOT 4602 AT fe2 DOT texas DOT rr DOT com> <Q7nbc.11457$Tx6 DOT 8473 AT fe2 DOT texas DOT rr DOT com>
NNTP-Posting-Host: accip02.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1080988698 8940 137.226.33.41 (3 Apr 2004 10:38:18 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 3 Apr 2004 10:38:18 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Bryan Parkoff <bryan DOT nospam DOT parkoff AT nospam DOT com> wrote:

>     The only one problem is that I am not allowed to include *.h (header
> files) into RHIDE's project group otherwise error message says, "Don't know
> how to build "*.h".  

That's primarily a target conflict.  Putting files into the project is
how you teach RHIDE which ones to *compile*, not as a shortcut to
opening them.

I haven't even tried to use RHIDE myself in ages, being a firm
believer in emacs and makefiles, but I seem to remember the
recommended method to edit header files in this kind of IDE is to open
one of the source files including them and then typing a special
hotkey with the cursor on their filename (Ctrl-Return?).

This organization makes more sense with C programs, where you almost
certainly wouldn't ever start a modification by editing a header file,
but rather have to update the header after you made some change to the
source, so it's natural to jump from the source to the header.  C++ is
different because it has inline member functions in the headers.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.