Re: [racket] Problem passing a reference

2012-09-17 Thread Ryan Culpepper
On 09/17/2012 03:35 PM, Kieron Hardy wrote: Is there actually a reason to use 'set!'? There is a period of time between creating the message and actually processing the message. Other events may cause the message to be abandoned. Therefore I think the set! is required, but maybe there's a

Re: [racket] Problem passing a reference

2012-09-17 Thread Kieron Hardy
> Is there actually a reason to use 'set!'? There is a period of time between creating the message and actually processing the message. Other events may cause the message to be abandoned. Therefore I think the set! is required, but maybe there's a better solution. Also, it's suspicious that your

Re: [racket] Problem passing a reference

2012-09-17 Thread Ryan Culpepper
On 09/17/2012 02:32 PM, Kieron Hardy wrote: Hi all, In the following fragment, I'm trying to create a new event, queue a callback to some handler to process that event, and then clear the event. (define/private (create-message) ... (set! the-event (new some-event%)) ...