I just pushed a commit that fixes this, as well as a test case based
on your example. Sorry for the problem.
Jay
On Tue, Oct 4, 2016 at 6:16 PM, Philip McGrath wrote:
> In #lang web-server, set! seems to behave differently with local vs.
> top-level variables. For
On 10/03/2016 06:38 PM, Jack Firth wrote:
So I'm reading a file in as code and expanding it, then looking for values in a
certain
syntax property that macros in the expanded code attach. This works fine for
prefab
structs, but I can't seem to get it to work with transparent structs. The issue
In #lang web-server, set! seems to behave differently with local vs.
top-level variables. For example:
> #lang web-server/base
(define x 0)
> (displayln x) ;; displays 0
> (set! x (add1 x))
> (displayln x) ;; displays 1
> (let ()
> (define y 0)
> (displayln y) ;; displays 0
> (set! y (add1
Thanks Vincent :)
On Mon, Oct 3, 2016 at 7:42 PM, Vincent St-Amour <
stamo...@eecs.northwestern.edu> wrote:
> `codeblock-pict` should do what you want, assuming there's a
> corresponding #lang (doesn't need to be a full implementation, just
> needs a lexer).
>
> Alternatively, you can use my
Hi Jack, Thanks for your reply. Setting breakpoints is not the
problem. The problem is to set things up so that when an *error*
happens, you end up in a paused state. You don't know in advance
where/when the error is going to happen. It might not always be at
the same location or every time
I'm not sure about how to do this with the DrRacket debugger, but you can use
`debug-repl`[1] from the `debug` package to basically set a breakpoint that
opens a REPL you can use to inspect variables in. This works in both DrRacket
and regular command line racket.
[1]
6 matches
Mail list logo