Mail Archives: djgpp/1999/08/24/23:53:45
As I said this may only be a feature of Rhide that I think should be added,
but it would be of good assistance to me and to people who pour questions
into the mailing list over the months asking about an error message that
they can't figure out. Either because people don't understand what it means
or are doing something which they dont realize is wrong. I agree a
programmer should learn their error messages and I'm not suggesting
changing them, some are so simple all you have to do is read. Never the
less if you could simply double-click on the text and you could get more in
depth info like telling you what it means and possible reasons why your
code is recieving this message debugging would then be more enjoyable, and
the next time they got the message they would understand. There is nothing
wrong with making information easier to get at, expecially when it comes to
debugging witch can be very annoying if you can't figure out whats wrong.
Yes, you are right alot of people do not look at the documentation, one
great feature with Rhide is that I can use my right mouse button highlight
a function or search and get info on how to use it. I didn't have to go
digging through huge text documents or page through a book on C. I can
find out about all the dpmi functions, syntaxes and return values that I
forget, plus an example on how to use the function. People can't remember
everything and the better everything is documented the funner and faster
learning is. Am I right? now, all thats left if someone doing all the
documentation =).
from ((--Dan Gold--))
----------
> From: Johan Venter <jventer AT writeme DOT com>
> To: djgpp AT delorie DOT com
> Subject: Re: Do Error Messages Really Help?
> Date: Tuesday, August 24, 1999 1:45 AM
>
> 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 -