Xref: news2.mv.net comp.os.msdos.djgpp:7219
From: "Maan M. Hamze" <mmhamze AT mail DOT utexas DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE and DJGPP
Date: 13 Aug 1996 18:07:22 GMT
Organization: University of Texas at Austin
Lines: 27
Message-ID: <01bb8942$3ea88920$a5cc5380@maan-m.-hamze>
References: <320FC47B DOT 4AB1 AT mindspring DOT com>
NNTP-Posting-Host: slip-11-5.ots.utexas.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Joshua Cannon Butcher <lchandar AT mindspring DOT com> wrote in article
<320FC47B DOT 4AB1 AT mindspring DOT com>...

> 1)	When you put, for example a directory path in for the INCLUDE files,
> and then you go to modify it, the existing INCLUDE DIRECTORY PATH DOES
> NOT SHOW UP IN THE TEXT BOX!

I believe this info is saved when you are using a project.
> 
> 3)	If there is no project file open, it WILL NOT (or I cannot get it to)
> create the .EXE file, only the .O file, this is severly lacking.

Try to do it as a project.  You get used to it!  I did!
> 
> 6)	Why call them projects and then make their extension .GRP?  Thats a
> Windows Group File.

hmm...... 
> 
> 7)	And for everyone in General, why do you have to stray away from
> industry standards?  Calling object files .O files instead of .OBJ,
> calling C++ files .CC instead of .CPP, and .a instead of .LIB for
> library. 

These are standard names in the Unix world!
>