parrot-dev Digest, Vol 46, Issue 6

[Bart Wiegmans]

> Date: Tue, 5 Jun 2012 07:30:56 -0400 (EDT)
> From: Andy Dougherty <doughera at lafayette.edu>
> To: Moritz Lenz <moritz at faui2k3.org>
> Cc: parrot-dev at lists.parrot.org
> Subject: Re: parrot-dev Digest, Vol 46, Issue 1
> Message-ID:
>        <alpine.DEB.2.00.1206050718390.29300 at fractal.phys.lafayette.edu>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Sat, 2 Jun 2012, Moritz Lenz wrote:
>
> It's worth remembering that both ffi and dyncall generally assume gcc on
> Unix-like systems, so their portability is somewhat limited.  (This is
> understandable, since the problem they are trying to address is hard.)
> That may not matter much at this particular stage of this particular
> project, but it's worth keeping in mind for the long run.
>
> --
>    Andy Dougherty              doughera at lafayette.edu
>
>

That is good to know, although I expect running mod_parrot within
windows will generally be rather tricky, what with different
incompatible VC versions flying arround. The alternative strategy is
to create a custom pmc, in which case neither dlfunc nor NCI will be
needed, as the dynamic linking is then done by the operating system.

Regards,
Bart Wiegmans