Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose functionality for eval in local scope #69

Closed
toivoh opened this issue Mar 28, 2015 · 1 comment
Closed

Expose functionality for eval in local scope #69

toivoh opened this issue Mar 28, 2015 · 1 comment
Labels
enhancement

Comments

@toivoh
Copy link
Owner

toivoh commented Mar 28, 2015

Most of the code in Debug.jl is actually devoted to making it possible to evaluate code in a local scope (through instrumentation, analysis, etc). This is currently only used to evaluate expressions in debug sessions. It would be nice if this functionality could be exposed for wider use.

Possible approach:

  • Introduce a macro @localscope, which evaluates to the Scope representing the local scope, when used inside of @debug
    • Make it raise an error otherwise?
  • Introduce a macro @debug_analyze which works like @debug and allows @localscope but doesn't emit any traps
  • Make @debug_analyze not introduce any more instrumentation than necessary
toivoh added a commit that referenced this issue Mar 28, 2015
@toivoh
Add @localscope macro for #69
f70163b 
* Add `code_analyzed_only` function to be used by macros that only make sense inside analyzed code
    * The code throws an error with custom message in the normal case
    * Make `decorate` recognize it and unwrap the payload instead
* Add `@localscope` macro that evaluates to the local scope
    * Make it produce a new node type `GetLocalScope` wrapped in `code_analyzed_only`
    * Make `instrument_args` emit the local scope symbol for `GetLocalScope`
* Add a `keys` method for `Scope`, returning its set of local variables
* Add simple test

Also change `Debug.Meta.quot` to produce a `QuoteNode`.
toivoh added a commit that referenced this issue Mar 28, 2015
@toivoh
Add a macro that never traps for #69, test with
989c5f1
toivoh added a commit that referenced this issue Mar 28, 2015
@toivoh
Make instrumentation not create Scope instances that will not be used…
a64dbd8 
…, for #69
toivoh added a commit that referenced this issue Mar 28, 2015
@toivoh
Fix mistake in for #69, and update test
53530e1
toivoh added a commit that referenced this issue Mar 28, 2015
@toivoh
Update README.md for #69, and put examples in a separate directory
41d1061
@toivoh
Copy link
Owner Author

toivoh commented Mar 28, 2015

This seems to be working now

@toivoh toivoh closed this as completed Mar 28, 2015
toivoh added a commit that referenced this issue Mar 28, 2015
@toivoh
Add nicer error message for variable not found in a scope for #69
a8e5946
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toivoh