Re: Re: Dialogs and inheritance
- To: mathgroup at smc.vnet.net
- Subject: [mg76606] Re: [mg76497] Re: [mg76417] Dialogs and inheritance
- From: Sseziwa Mukasa <mukasa at jeol.com>
- Date: Thu, 24 May 2007 06:19:49 -0400 (EDT)
- References: <200705220640.CAA19062@smc.vnet.net> <200705230920.FAA23723@smc.vnet.net>
On May 23, 2007, at 5:20 AM, Lev Bishop wrote:
> On 5/22/07, alexxx.magni at gmail.com <alexxx.magni at gmail.com> wrote:
>> Hello,
>> I'm trying to learn to use Dialogs for debugging purposes - since I
>> cannot learn the right way to use the integrated debugger.
>> Can you please tell me what is wrong in the following???
>>
>> In[1]:= Module[{a},
>> Do[
>> a = {i, Sin[i]};
>> Dialog[],
>> {i, 100}]]
>>
>> (Dialog) In[2]:= i
>>
>> (Dialog) Out[2]= 1
>>
>> (Dialog) In[3]:= a
>>
>> (Dialog) Out[3]= a
>>
>> I thought under Dialog I could be able to see all the local values of
>> the variables!
>
> In the documentation, tutorial/HowModulesWork has an example just
> like this.
To expand on that statement, within a Module statement the actual
names of the local variables are the name specified in the first
argument and a string of the form $n where n is a number. You can
find the value of n by doing Names["a$*"].
>> P.S. any hint on where to start with the integrated debugger? The V6
>> guide: guide/TuningAndDebugging is rather limited...
If you have an expression that generates a message turn on
breakpoints on all messages then evaluate the expression. You can
then use the integrated debugger to see the call stack, step through
evaluation etc.
Regards,
Ssezi
- References:
- Dialogs and inheritance
- From: "alexxx.magni@gmail.com" <alexxx.magni@gmail.com>
- Re: Dialogs and inheritance
- From: "Lev Bishop" <lev.bishop+mathgroup@gmail.com>
- Dialogs and inheritance