From: "Fábio Diales da Rocha" Newsgroups: comp.os.msdos.djgpp Subject: Re: RHIDE - compliments and complaints Date: Wed, 17 Dec 1997 13:09:34 -0000 Lines: 87 Message-ID: <678ing$vh2$1@duke.telepac.pt> References: <67790n$372$1 AT duke DOT telepac DOT pt> <349771B6 DOT F74803A1 AT LSTM DOT Ruhr-UNI-Bochum DOT De> NNTP-Posting-Host: 194.65.180.55 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Thomas Demmer wrote in message <349771B6 DOT F74803A1 AT LSTM DOT Ruhr-UNI-Bochum DOT De>... >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). Well, i have version 1.4 and it still doesn't work. >> 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 > What i mean is just that i want to normally open a file, in any directory and then compile it straight away. The problem with RHIDE is that if i do that it says it can't find the file. So, to get it to compile i have to close rhide, change de dir, reopen RHIDE and compile. Either that or i had it to the Source Dir. This is extremly annoying. >> 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? A 200 mhz Pentium MMX with 32 MB of ram. Rhide reports something like 25M/120M. And it's not just grep. GCC to. And every other program i call from rhide. If i try to compile something with just one source file it calls gcc twice (to compile to .O and to .EXE) it takes about a 40 seconds to do it. >> 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. [...] >but this is a matter of personal preferences... Yes, but i don't like that way, and i'm sure that a lot of programmers don't (and others do) and the identing should be customizeble. >> 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. >> >Depends on what you consider the "next version" ;-) Something like 1.5 or 1.4.1 Fábio Diales da Rocha