From:	abarak AT iil DOT intel DOT com (Amit Barak)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: misfeature in RHIDE ?
Date:	6 Feb 1997 11:35:36 GMT
Organization:	Intel Israel (74) Ltd.
Lines:	61
Message-ID:	<5dcfm8$1c77@www.iil.intel.com>
References:	<Pine DOT A32 DOT 3 DOT 93 DOT 970205103205 DOT 46098A-100000 AT ilx214 DOT iil DOT intel DOT com> <32F8782E DOT 479C AT Mathematik DOT tu-chemnitz DOT de>
NNTP-Posting-Host:	ilx214.iil.intel.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Robert Hoehne (Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de) wrote:
: Amit Barak wrote:
: > 
: > Salvador,
: > 
: > Thanks, but this is not exactly what I needed.
: > The disadvantage of the method you describe is that you can not
: > use the same filename more than once (each time is different directory)
: 
: That's correct.
: 
: > 
: > In Borland C++ 3.1 for example, you can include files path in the project
: > file for individual file e.g "c:\a\b.c"
: > 
: 
: OK. Can you tell me a real good reason for have multiple files
: with the same same name but in different directories?
: 
: Imagine RHIDE would have the aibility to inlcude also the pathnames
: in your project, then you will get the next problem. You will
: not be able to debug the program, since the COFF debugging
: information is limited to only the filename and not the 
: directory. So when you debug the program (within RHIDE
: or with GDB), from where should the debugger know, for
: which file it should show the lines beeing debugged?
: 
: Robert
: -- 
: *****************************************************************
: * Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
: * Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
: * e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
: * WWW:     http://www.tu-chemnitz.de/~rho                       *
: *****************************************************************

I'm honored ...

Well, I cannot argue with the debugging problem you mention here,
as for your other question -
I actually needed this feature while I ported (still working on it..)
a project from 16 bit BC3.1 to DJGPP. The project includes (F)LEX scanner
and I liked the idea of keeping everything related to this scanner in
a different subdirectory. I can also think of projects that include more
than one scanner, with many lexyy.c's, to me it looks convenient to use
a different subdirectory for each scanner and not have to rename lexyy.c,
of course, there are workarounds for all the problems I mentioned, and I am
not suggesting this is a giant major bug/misfeature - just one of those
nice to haves.

One other point - even if all source files do have unique names, but some
are not in the working directory, it is sometimes nice to be able to see
that information directly from the project file window.

Cheers!

-- 
 amit barak
 intel israel (74)
 voice: 972-4-865-6010
 email: abarak AT iil DOT intel DOT com

- Raw text -