I tried to use this program to break things:
#lang racket
(begin-for-syntax (sleep 5))
(+ 1 2)
which should behave something like what you're saying and might give
an opportunity for a race in the GUI to appear, but that didn't seem
to do it for me.
I'll keep my eyes open, tho. I may just not be
On Monday, January 30, 2017 at 1:43:06 PM UTC-8, Robby Findler wrote:
The simple program seems to work ok.
It appears my problem is related to bytecode compilation (this occurs on a
smallish program that pulls in a large library)... it takes awhile for the
buttons to respond, and it seems like
It isn't an issue I know about.
I don't see that with this simple program:
#lang racket
(let loop () (loop))
Do you?
Robby
On Mon, Jan 30, 2017 at 2:12 PM, Dan Liebgold
wrote:
> I'm having trouble with the debugger in DrRacket: I'll start it and the
> debugger buttons available at the top w
> On May 16, 2016, at 4:48 PM, Braids Constance wrote:
>
> On Sunday, May 15, 2016 at 10:26:41 PM UTC-4, Braids Constance wrote:
>> second, i'd like to see DrRacket display the value of the most recently
>> evaluated expression.
>
> after reading about expression level breakpoints in DrRacket,
Just mention here:
I met this error message when invoking a function with keyword arguments
within the class body (but not method body).
The simplest solution is to wrap the function application in another
function that do not passed with keyword arguments.
(define toolbar-snip% : Toolbar-Snip%
5 matches
Mail list logo
