Date: Sun, 8 Aug 1999 14:11:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: David Oppenheimer <davidopp AT megsinet DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: RawHIDE
In-Reply-To: <37A9C270.AF35B1B9@megsinet.net>
Message-ID: <Pine.SUN.3.91.990808141045.23423T-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 5 Aug 1999, David Oppenheimer wrote:

> Say good bye to your rawhide problems and spend time coding instead
> of wasting time trying to figure out how to use rawhide.

And say goodbye to the built-in debugger that is part of RHIDE.  Say
hello to the good old printf debugging and guesswork instead!  (Who
said we need any debugging, anyway?)

Also say goodbye to launching DJGPP programs from within the editor
with virtually unlimited command lines; say hello to the dreaded
126-character limit of COMMAND.COM!

These are only two important features that you will lose if you turn
away of an IDE compiled with DJGPP to anything else.  There's more to
lose down that road.

Note that I myself don't use RHIDE, so you can't accuse me of any
prejudice towards RHIDE.  But telling people to toss a good tool just
because they couldn't be bothered to read the README file is IMHO too
extreme.