, August 5, 2013 3:09:50 PM GMT -05:00 US/Canada Eastern
Subject: Re: [racket-dev] Too many struct definitions leads to literal
local-code error
Seeing #local-code is about the same as a seg fault.
Can you send me something to replicate the crash on my machine?
On Aug 5, 2013, at 11:55 AM
Johnson i...@ccs.neu.edu
Cc: dev dev@racket-lang.org
Sent: Monday, August 5, 2013 3:09:50 PM GMT -05:00 US/Canada Eastern
Subject: Re: [racket-dev] Too many struct definitions leads to literal
local-code error
Seeing #local-code is about the same as a seg fault.
Can you send me something
Just pulled and rebuilt. No go.
I'm not defining an insane amount of structs. It's at 19 or so that this starts
being a problem. I am in a splicing-syntax-parameterize context, which might be
where the problems are being introduced.
-Ian
- Original Message -
From: J. Ian Johnson
Seeing #local-code is about the same as a seg fault.
Can you send me something to replicate the crash on my machine?
On Aug 5, 2013, at 11:55 AM, J. Ian Johnson i...@ccs.neu.edu wrote:
I'm working more on my analysis framework, and added many different kinds of
new continuation frames. I
. Ian Johnson i...@ccs.neu.edu
Cc: dev dev@racket-lang.org
Sent: Monday, August 5, 2013 3:09:50 PM GMT -05:00 US/Canada Eastern
Subject: Re: [racket-dev] Too many struct definitions leads to literal
local-code error
Seeing #local-code is about the same as a seg fault.
Can you send me something
5 matches
Mail list logo
