From:	Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: RHIDE - compliments and complaints
Date:	Wed, 17 Dec 1997 07:31:18 +0100
Organization:	Lehrstuhl fuer Stroemungsmechanik
Lines:	107
Message-ID:	<349771B6.F74803A1@LSTM.Ruhr-UNI-Bochum.De>
References:	<67790n$372$1 AT duke DOT telepac DOT pt>
NNTP-Posting-Host:	bvb.lstm.ruhr-uni-bochum.de
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Fábio Diales da Rocha wrote:
[...]
>     Despite that there are 3 "undocumented features" that I find quite
> unpleasant:
> 
>     1. It refuses to compile "cpp" files, only accepting "cc" ones although
> gcc does fine with "cpp" files
AFAIK this is fixed at least since version 1.4 (rather before).

> 
>     2. Its complete inability to find files in the current directory,
> forcing you to add it to the search directories. And, NO, i don't like
> projects, they're perfectly supportable if you're actually coding something,
> but if you want just to browse through some source files they're completly
> insupportable.
I do not really understand what you mean. The situation when you press
F3?
Here 1.4 remembers the last directory you were in when you opened a
file.
If this isn't your cwd, just get back there. If you mean when compiling, 
you may have checked Directories in project items in
Environment/Options.
If you mean inluded files, just use #include "foo" instead of #include
<foo>

> 
>     3. And last, but certanly not least - it takes an unnecessary ammount of
> time to compile because it spends half the time writting and reading
> something to disk. Example: if just try to run grep (i don't have it) it
> takes about 15 seconds before a simple "Bad command or file name". This is
> extremelly annoying. Believe it or not i've read a book in the interims
> rhide takes to call gcc twice.

Hmm. This looks like a screwed up memory configuration. I saw this
only once with a machine having 16kB (!) free DPMI memory after starting
RHIDE (some weird memory manager). Usually, calling grep works
immediately. What does the free memory indicator say?
What is the general setup of your machine?

> 
>     That and some minor inconcistences on the keyboard mapping and the
> intelligent identing (remember, you can identify a programmer by the way he
> idents is code, so very obtrusive intelligent identing is very irritating)
> stop RHIDE from being the perfect IDE.
You can change the kb mapping wildly to your free will. The indenting
is in fact not what I personally like, but mostly consistent. 
I like
   if (whatever){
     foo();
   }
   else{
     bar();
   }

whereas RHIDE supports
   if (whatever)
   {
      foo();
   }
   else
   {
      bar();
   }

but this is a matter of personal preferences...


>     I hope these glitches will be fixed by the next version and please tell
> me if some of the "bugs" I mencioned are in fact something I'm doing wrong.
> 
>     Fábio Diales da Rocha
Depends on what you consider the "next version" ;-)


-- 
Ciao
Tom

*************************************************************
* Thomas Demmer                                             *
* Lehrstuhl fuer Stroemungsmechanik                         *
* Ruhr-Uni-Bochum                                           *
* Universitaetsstr. 150                                     *
* D-44780  Bochum                                           *
* Tel: +49 234 700 6434                                     *
* Fax: +49 234 709 4162                                     *
* http://www.lstm.ruhr-uni-bochum.de/~demmer                *
*************************************************************

- Raw text -