Re: Re: debugging

*To*: mathgroup at smc.vnet.net*Subject*: [mg56742] Re: [mg56694] Re: [mg56676] debugging*From*: "Hermann Schmitt" <schmitther at t-online.de>*Date*: Thu, 5 May 2005 06:01:24 -0400 (EDT)*References*: <200505030926.FAA25668@smc.vnet.net> <200505040433.AAA06152@smc.vnet.net> <2369bb683dd911a8e2b5e3cb70d599e6@mit.edu>*Sender*: owner-wri-mathgroup at wolfram.com

Hello dan, what do you want to see? Write a program, which has the following statement as first statement: $MessagePrePrint = (Print["Error -> Quit"]; Quit[])&; (The right side of the assignment statement is a "pure function") Then write some statements, one or more of which are erroneous and some Print statements between. Hermann Schmitt ----- Original Message ----- From: "Daniel Roy" <droy at MIT.EDU> To: mathgroup at smc.vnet.net Subject: [mg56742] Re: [mg56694] Re: [mg56676] debugging > i would be interested in seeing that if possible > > dan > > > On May 4, 2005, at 12:33 AM, Hermann Schmitt wrote: > > > Hello, > > I wrote an OO System for Mathematica. The program has 900 lines. I had > > the > > same problem as you, but now I found out the following: > > If the following statement is executed: > > $MessagePrePrint = (Print["Error -> Quit"]; Quit[])&; > > the program is finished, when the error message is prepared. Otherwise > > the > > program does not finish and it is difficult to find the statement in > > error. > > If the program has no output, you have to insert Print statements, to > > see, > > what was executed and what was not executed. > > > > ----- Original Message ----- > > From: "Daniel Roy" <droy at mit.edu> To: mathgroup at smc.vnet.net > > Subject: [mg56742] [mg56694] [mg56676] debugging > > > > > >> > >> 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 > >> > > >

**References**:**debugging***From:*Daniel Roy <droy@mit.edu>

**Re: debugging***From:*"Hermann Schmitt" <schmitther@t-online.de>