[racket-dev] "Too many" struct definitions leads to literal error

2013-08-05 Thread J. Ian Johnson
I'm working more on my analysis framework, and added many different kinds of new continuation frames. I get to a point where I comment out all definitions past a certain point (and their uses) and the program compiles. I add one more (any one) and I get the following error: kcfa-instantiations.

Re: [racket-dev] "Too many" struct definitions leads to literal error

2013-08-05 Thread J. Ian Johnson
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" To: "d

Re: [racket-dev] "Too many" struct definitions leads to literal error

2013-08-05 Thread Matthew Flatt
Seeing # 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" wrote: > I'm working more on my analysis framework, and added many different kinds of > new continuation frames. I get to a point where I c

Re: [racket-dev] "Too many" struct definitions leads to literal error

2013-08-05 Thread J. Ian Johnson
Pushed current branch to https://github.com/dvanhorn/oaam/tree/thocon kcfa.rkt has an "mflatt" comment that will point you at the problem lines of code. The entry point for the project is kcfa-instanstantiations.rkt -Ian - Original Message - From: "Matthew Flatt" To: "J. Ian Johnson" C