Sender: "Rolf Campbell" <cp1v45 AT nortelnetworks DOT com>
Message-ID: <379C738B.5FD0736F@americasm01.nt.com>
Date: Mon, 26 Jul 1999 10:41:16 -0400
From: "Rolf Campbell" <cp1v45 AT nortelnetworks DOT com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.6 [en] (X11; I; HP-UX B.10.20 9000/712)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
To: djgpp AT delorie DOT com
Subject: Re: Strange localtime function behaviour
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990726155255 DOT 22556A-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Orig: <cp1v45 AT americasm01 DOT nt DOT com>
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:

> (I wonder why people always bring up Borland as an example that DJGPP
> should follow?  It has much less functionality and much more bugs...)

    It is probably because many people start with Borland C++ v3.1 (it is
taught in many universities).
What bugs have you found in Borland C/C++?   I did notice a few automatic
variable allocation bugs (2 local variables would get the same location on the
stack occasionally).
I have found that it's compiler error messages are much less cryptic.  I
understand how hard it is to make decent parse-error messages using Bison, my
only conclusion is that they didn't use Bison to do their parsing.  Also, I
liked the way Borland's help pages offered help on more than just function
calls.  I have been meaning to try writing some info files for DJGPP that do
just that, but I don't know where I can get a good program for writing info
files.  Or at least documentation on the format.  Can someone point me in a
direction?

--
     -Rolf Campbell (39)3-6318