Dynclasses are broken on Windows for two reasons: 1) Missing exported symbols If the powers that be give me a sign how it should be done, I'll gladly implement it.
What do people think of my previous proposal? Is it any good? " How about this: We separate things into 2 steps. 1) Create a .sym file for each relevant compilation unit(s). 2) Join the .sym files for all to-be-linked objects and create the .def file. (on Windows) Now things boil down to creating the .sym files. These might be created by grepping the source for C<nci_>, C<Parrot_>, etc, or by whatever script created the compilation unit(s). " 2) Static linkage Dynclasses are currently statically linked against libparrot.lib, thereby using their own (uninitialized) parrot. Ron
