Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2005
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*November
*December
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2005

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: debugging

  • To: mathgroup at smc.vnet.net
  • Subject: [mg56687] Re: debugging
  • From: dh <dh at metrohm.ch>
  • Date: Wed, 4 May 2005 00:32:52 -0400 (EDT)
  • Sender: owner-wri-mathgroup at wolfram.com

Hi Daniel,
(there seem to be quite a lot "Daniels" around in this group!").
Well, if you have 50+ lines on the same level you should consider to 
make your program more modular and hierarchical. This way you will have 
a top program (or function) that calls some other functions e.t.c
Debugging the top function allowes you to locate the error coarsly. You 
then debug the corresponding subfunction e.t.c. Every function should be 
rather short, say 10 to 20 lines. Using this approach, Print statements 
are often good enough for debugging.

If you want a real and free debugger, look at the following link:
http://www.dbaileyconsultancy.co.uk/debugger/debugger.html

Sincerely, Daniel

Daniel Roy wrote:
> My question concerns debugging.  I've done googling to find a quick
> answer but have failed.  I'm developming large functions and without
> line numbers telling me where the errors occurred, its becoming very
> difficult to develop code quickly.  Can anyone point me in the right
> direction in terms of debugging multi line  (at least 50+ lines)
> functions?
> 
> thanks,
> dan
> 


  • Prev by Date: garbage collection and netlink
  • Next by Date: Re: Re: Summation problem
  • Previous by thread: Re: debugging
  • Next by thread: Re: Re: debugging