----- Original Message -----
From: "Pablo Manalastas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 16, 2002 8:07 AM
Subject: Re: [plug] GUI and UP CS
>
> On Tue, 15 Jan 2002, Sacha Chua wrote:
>
> > However, we don't really teach good programming and debugging practices
> > in school. <ruefully> Even the teachers tend to use printfs to 'debug'
> > their code. I'd like to change that.. should be fun, you think?
>
> Ideally, your program should already be error free and thoroughly
> debugged, even before you sit down to type the code. We did
> "paper debugging" in the late 1960s, and the thing worked for us,
> and I do not see why it should not work for you today.
> I believe that paper debugging is a good programming practice. It takes
> you away from the monitor and its dangerous radiation. It gives you time
> to think out your program, which you should have done in the first place!
dont tell us to print our code in paper and do the debugging there :-> hey
this is not the era of fortran (paper programming) anymore :-> if you think
radiation is a threat to you then buy a low radiation monitor plus a monitor
screen filter that will save you a couple bucks and development time in the
long run than buying a paper. :->
as i said time change, people change, technology change... if you dont
believe in this, you are going to be left behind... people are always find
solutions to ease their lives... that is why IDE (Integrated Development
Environment) exist to ease their debugging and development time... one good
example of IDE is borland's IDE.. you got all the tools for your debugging
needs. example, breakpoints, watchpoints, step by step tracing, machine
codes and etc... sometines i dont usually understand some of the people
hates IDE :->
what causes of debugging? because of errors...what are those errors? well
there are three types of errors as far as i can remember:
1. logical errors
2. compile-time errors
3. run-time errors.
logical errors - everything starts with the human, your computer is only
waiting for your command and computer dont makes mistakes! humans do... one
of the good example of logical error is that you have the wrong output due
to wrong computation.
compile-time errors - usually this kind of error doesnt conform to its
grammar rules during compilation... example, assigning string data types to
numeric data types and vice versa.. wrong passing of arguments and many
more...
run-time errors - this error only exist during running your program... yes,
you have logically and grammatically correct but suddenly an error exist...
so what happen? one of the good example is, asking an user input for its
divisor, and then user input a zero, and there you go, you have a division
by zero run-time error... and many more....
> On Tue, 15 Jan 2002, Sacha Chua wrote:
>
> > However, we don't really teach good programming and debugging practices
> > in school. <ruefully>
sacha,
programming is a dynamic learning state, dont heavily rely to your
teachers waiting to teach you good programming.. they will only teach you as
to their maximum capacity... learn and go beyond that barrier.
fooler.
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
