There were more problems --- now fixed.
At Mon, 24 May 2010 08:44:05 +1000, Paul Steckler wrote:
> Thanks, I'll try that out.
>
> -- Paul
>
>
> On 5/23/10, Matthew Flatt wrote:
> > I forgot to update MzCOM for a new requirement (to support futures) on
> > embedding MzScheme into a Windows exec
Thanks, I'll try that out.
-- Paul
On 5/23/10, Matthew Flatt wrote:
> I forgot to update MzCOM for a new requirement (to support futures) on
> embedding MzScheme into a Windows executable.
>
>
> I'll try this myself, but if you get to it first, try adding
>
> static __declspec(thread) void *t
I forgot to update MzCOM for a new requirement (to support futures) on
embedding MzScheme into a Windows executable.
I'll try this myself, but if you get to it first, try adding
static __declspec(thread) void *tls_space;
to the MzCOM executable, and then put
scheme_register_tls_space(&tls_
Erich Neuwirth had written to me that MzCOM from the latest PLT
release crashed for him, so I went off to investigate. I hadn't run
MzCOM (or MysterX) in yonks (as they say here).
I compiled MzCOM from sources using Visual Studio 2008, no issues
there. I couldn't get MysterX (libmysterx)
to comp
