[plt-scheme] 372: 3m does not check for VirtualAlloc failure

From: Eric Kidd (eric.kidd at iml.dartmouth.edu)
Date: Thu May 8 07:43:47 EDT 2008

On Thu, May 8, 2008 at 3:09 AM, Noel Welsh <noelwelsh at gmail.com> wrote:
>  FWIW, we found compiling (on the command line, with mzc -k) was
>  something like O(n^2) in the number of files in 372.  It would slow
>  down significantly on large projects. 3.99 is *much* better in this
>  regard.

Thank you for that information! If that's the case, than I have two
questions about 3.99:

1) How stable is 3.99? I've seen a few segfault reports on the mailing
list, which would suggest that it might be too soon for us to consider

2) Assuming we have ~2000 lines of C++ code using the 372 3m API, and
~100,000 lines of Scheme code using the mzscheme language, what would
be involved in upgrading to 3.99? We're definitely not interested in
moving to R6RS any time in the next 6 months.

I've poked around the website a bit, but I haven't found a "porting to
3.99" document yet.

Thank you for any pointers you can provide!


Posted on the users mailing list.