Ron Blaschke <mailing-lists@xxxxxxxxxxx> wrote:
> 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).
Not everything that starts with Parrot_ is an API (e.g. opcode
functions). I think an explicit macro PARROT_API should denote
exportable symbols.
> 2) Static linkage
> Dynclasses are currently statically linked against libparrot.lib,
> thereby using their own (uninitialized) parrot.
Yeah. Linux needed -Wl,-E in LINKFLAGS to convince the linker to do the
right thing.
> Ron
leo
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
