Leopold Toetsch wrote:
> Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> Leopold Toetsch wrote:
>> If I would be the one to choose, I'd add the C 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 g
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 macro
Leopold Toetsch wrote:
> Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> Now things boil down to creating the .sym files. These might be
>> created by grepping the source for C, C, etc, or
>> by whatever script created the compilation unit(s).
> Not everything that starts with Parrot_ is an API (e.g.
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Now things boil down to creating the .sym files. These might be
> created by grepping the source for C, C, etc, or
> by whatever script created the compilation unit(s).
Not everything that starts with Parrot_ is an API (e.g. opcode
functions). I think an
