From:	"Josh Anderson" <randerso AT win DOT bright DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Some RHIDE problems
Date:	9 Feb 1997 02:51:18 GMT
Organization:	BrightNet Wisconsin
Lines:	39
Message-ID:	<01bc1633$a3c6f700$ee038cd0@wahander>
NNTP-Posting-Host:	mil1-cs-13.win.bright.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Okay, two BIG prolems with RHIDE. And one small one. 

note: I am using the bugfix 1.1 version

First: the small one
Sometimes when I am typing in RHIDE lines just dissapear. And some others
are repeated on lines that are supposed to be blank. It's really annoying,
and impossible to tell if this blank line is actually a line of code or
not. 

Next: The first big one, smaller of the two
When I write code, I like to have stuctured loops. For every loop I just
hit tab to go in. Makes it a little easier to tell what code belongs to
what loop. Well, ever now and then, when I save it that whole stucture is
ruined. Some lines have more white spaces than they had before, and some
have less than they did. And it takes FOREVER to go through and fix this.

Third: Traceback eips don't work right
Well, only if it's in an included file. Okay pseudo code example.

main.c

#include "somefile.c"

main
......

so it crashes on say line 500 in somefile.c. RHIDE follows the traceback
eip. It says file (main.c) line 500. So RHIDE just puts it to line 500 of
main.c. If there is, if there isn't it just goes to the end. Sometimes
crashing. Well, I'm developing a 3D graphics library. And I've found that
it's quicker to just include the 3D files than to compile the library and
then link it in. So I have a lot of included files. And they crash a lot.
It gets really annoying to push F6 until the crashing file is in the
window. Then the message window has been hidden, so if i forgot to read the
code line, i have to find it again and then switch back to the included
file. It takes A LOT more time than it should.

- Raw text -