Ron Blaschke <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: >> Not everything that starts with Parrot_ is an API (e.g. opcode >> functions). I think an explicit macro PARROT_API should denote >> exportable symbols.
> I thought so, too. > If I would be the one to choose, I'd add the C<PARROT_API> macro > everywhere, and expand it to C<__declspec(dllexport)> on Windows (no > more .def files). I'd also provide a sample script that can be used > to get a .sym file (for whoever might need it). > I'll gladly implemement any solution you consider best, as Windows is > in desperate need for it All I need is a +1 from a comitter, to > avoid warnocked patches. First question is: should it be contained in 0.1.2? But these changes can't be done before Dan's string changes are merged to CVS HEAD. And WRT patches: please provide separate patches per subsystem - roughly the structure of the html docs' c.html. leo
