in reply to Re: Perl debugging - a look at 'beta' mechanism
in thread Perl debugging - a look at 'beta' mechanism

I build in a option of $verbose. This means I print out statements if $verbose. If I set $verbose to 0 I don't see the verbose output anymore.

I'm like tilly, I work on a test environment with a smaller dataset then on production.

I also break down the code to small subroutines I can test seperated. So afterwards when I do the whole integration test of my application, it's a test if the logic is right and not if I made a perl mistake...



--
My opinions may have changed,
but not the fact that I am right

  • Comment on Re: Re: Perl debugging - a look at 'beta' mechanism

Replies are listed 'Best First'.
Re: Re: Re: Perl debugging - a look at 'beta' mechanism
by metadoktor (Hermit) on Jan 11, 2002 at 17:06 UTC
    I build in a option of $verbose. This means I print out statements if $verbose. If I set $verbose to 0 I don't see the verbose output anymore.

    I use something similar. I sometimes have lots of if $debug statements if I need them. Once I'm finished I can delete them if I want.

    I also break down the code to small subroutines I can test seperated. So afterwards when I do the whole integration test of my application, it's a test if the logic is right and not if I made a perl mistake...

    This is also crucial. I always test the function that I've written against various boundary conditions and then integrate into the whole otherwise you get horrendous error messages in your program.

    Plus my two cents with regards to debuggers....I've done both print statements and have used a debugger and I have to say that I prefer print statements! I've always found debuggers a pain to use but YMMV.

    metadoktor

    "The doktor is in."

[reply]

In Section Meditations