Thanks. Applied.
On Sat, 3 Nov 2001, Jason Diamond wrote:
> Here's a minimal patch for the dynamic loading functions on Win32. I punted
> on properly implementing Parrot_dlerror for now but the other three should
> work.
>
> How soon can you check in your ops so we can test these?
>
> Jason.
Here's a minimal patch for the dynamic loading functions on Win32. I punted
on properly implementing Parrot_dlerror for now but the other three should
work.
How soon can you check in your ops so we can test these?
Jason.
diff
Description: Binary data
In article
<[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Andy Dougherty) wrote:
> On Fri, 2 Nov 2001, Jason Diamond wrote:
>
> > Then we could have a "driver" for each platform that consisted of
> > nothing
> > but #include's of other .c files. Making a directory for each
> > platform might
> > be
> > Okay, here's the updated scheme.
> >
> > *) There is a platform/generic.c and platform/generic.h. (OK, it'll
> > probably really be unixy, but these days it's close enough) If there is
no
> > pltform-specific file, this is the one that gets copied to platform.c
and
> > platform.h
> >
> >
On Fri, 2 Nov 2001, Dan Sugalski wrote:
> At 11:40 AM 11/2/2001 -0500, Andy Dougherty wrote:
> >What specifically do you expect might end up in linux.[hc] as opposed to,
> >say, solaris.[hc]? How many different *bsd.[ch] files do you propose? How
> >many different System V.4-derived platform fil
On Fri, 2 Nov 2001, Jason Diamond wrote:
> Then we could have a "driver" for each platform that consisted of nothing
> but #include's of other .c files. Making a directory for each platform might
> be appropriate if we do this. I bet that most of the posix "platform" source
> files would be #incl
At 11:40 AM 11/2/2001 -0500, Andy Dougherty wrote:
>What specifically do you expect might end up in linux.[hc] as opposed to,
>say, solaris.[hc]? How many different *bsd.[ch] files do you propose? How
>many different System V.4-derived platform files do you propose?
That's a very good question.
> What specifically do you expect might end up in linux.[hc] as opposed to,
> say, solaris.[hc]? How many different *bsd.[ch] files do you propose? How
> many different System V.4-derived platform files do you propose?
We could always rename linux.[hc] to posix.[hc] or something similar. Is
dlop
> I just checked in changes to platforms/linux.[hc] that add wrappers
> around the dynamic loading functions that work here.
Umm, this worries me a little as being too platform-specific. (Not to
pick on anyone in particular, this message just finally nudged me enough
to try to write down some th
