From:	"Johan Venter" <jventer AT writeme DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<199908232202 DOT SAA12175 AT delorie DOT com>
Subject:	Re: Do Error Messages Really Help?
Lines:	45
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-Mimeole:	Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID:	<pJvw3.4742$ei1.9960@newsfeeds.bigpond.com>
Date:	Tue, 24 Aug 1999 18:45:31 +1000
NNTP-Posting-Host:	139.134.163.220
X-Trace:	newsfeeds.bigpond.com 935495637 139.134.163.220 (Tue, 24 Aug 1999 21:53:57 EST)
NNTP-Posting-Date:	Tue, 24 Aug 1999 21:53:57 EST
Organization:	Telstra BigPond Internet Services (http://www.bigpond.com)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Dan Gold <TedMat AT CoastNet DOT com> wrote in message
news:199908232202 DOT SAA12175 AT delorie DOT com...
> I was thinking that often people get an error message that tells them
whats
> wrong, but then they dont understand the error message. Mayby a new
> direction would be to add examples, and other info along with these
errors.
>  Or mayby make the text clickable for some info.  This may only be part of
> Rhide or DJGPP I'm not sure who makes the callback text.  It would
> definately thin out the traffic on this mailing list.  Like a General
> Protection Fault is a reference to memory that your not supposed to touch
> from what I understand.  Don't get me wrong, I think a parse error is
> pretty self explanatory...=)

But learning what error messages mean that your compiler spits out and how
to debug them is part of programming in general. Every programmer that wants
to be able to make bug free programs (that's an oxymoron, but never mind
:-)) should learn that when your code gpfs you probably tried to reference
undeclared memory.

It doesn't matter that we answer questions that say "why does my code gpf"
with the same answer everytime, documenting things doesn't seem to work,
because many people just can't be bothered reading the documentation (as is
the case with the FAQ. BTW, people, read it! Make it your BIBLE!!! Do your
best to find your problem in the FAQ, as it's probably there and explained
in more detail than a relatively short newsgroup post could provide). I
think it better that we teach one programmer to look at the docs than to
teach a million to click on the error message and be told exactly what's
wrong with his code and how to fix it, at the same time as making him a
coffee and giving him a foot massage. Afterall, there's no limit to
traceback is there? :-))

DISCLAIMER: I may talk a lot of crap, but I hope I'm getting the main point
across. I don't take responsibility for any pain, suffering or irritation in
general that rise from reading my posts, nor do I claim that my opinions are
right or 100% accurate. Deal with it.

Peace (at least in the Mandela form :-)),
--
Johan Venter
ICQ 3643877
surf.to/djgppig

- Raw text -