Take the 2-minute tour ×
Mathematica Stack Exchange is a question and answer site for users of Mathematica. It's 100% free, no registration required.

Consdier the following package

BeginPackage["packageName`"];
   exportedFunction::usage = "...";
   Begin["`Private`"];
      globalVariable = Null;
      initializePackage[args___] := (globalVariable = workOn1[args]);
      exportedFunction[args___] := 
         Block[{localVariable},
            If[globalVariable===Null, Abort[]];
            localVariable = workOn2[globalVariable, args];
            workOn3[localVariable]
         ];
      workOn1[args___] := ...;
      workOn2[gv_, args___] := ...;
      workOn3[lv_] := ...;
   End[];
EndPackage[];

and assume that is being debugged in a workbench session, and that a break point has been set somewhere in exportedFunction. The debugger reports on the values of localVariable, but I can never see the value of globalVariable. Is there a way to inspect the value of globalVariable as well?

share|improve this question
    
    
@WReach: I think, though I might be wrong, that this post is not closely related to the example you linked. In the exapmpel that you are pointing to the variable (a) is local. I am asking specifically about global variables. Did I missunderstood something? –  zorank Mar 31 at 18:36
    
OK, I've added an answer to explain more fully. –  WReach Apr 1 at 13:42

1 Answer 1

up vote 3 down vote accepted

The Workbench's Expressions debugging view allows to evaluate any arbitrary expression, including global variables. While stopped at a breakpoint, press the Create a new watch expression button in the Expressions view and enter the name of the global variable as the expression. If the Expressions view is not visible, you can open it from the Workbench main menu using Window / Show View... / Expressions.

In contrast, if one wants to inspect a local variable x one must use the watch expression VariableValue[x].

We are not limited to referencing global and local variables. Any expression can be watched (see Inspecting non-variable state from a breakpoint in Workbench for a screenshot).

share|improve this answer
    
I understand finally! I tried it though, and could not make it work. The expression (a global private variable in the package) never evaluates. Do I have to reference with the full name (including the context)? –  zorank Apr 4 at 15:36
1  
@zorank Yes, a private variable would need to be fully qualified. For example, packageName`Private`globalVariable (from the question). –  WReach Apr 5 at 2:57
    
Domo arigato! It works! Just tested it. –  zorank Apr 7 at 9:19

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.