Here's my crazy idea.
When you register a callback into PIR from C, you need to pass a few
arguments: the interpreter into which to call, the PMC Sub to call, and the C
signature of the C function which gets called from C.
I presume that the PIR function will get called through one of the exter
On Friday 18 January 2008 20:25:16 Allison Randal wrote:
> It's true that the generalized solution for varying callback signatures
> doesn't exist yet, but it's easy enough to create your own C callback
> layer, with a separate C function for each callback you need. (Note, not
> one-per-signature,
On Sat, 2008-01-19 at 17:25 +1300, Allison Randal wrote:
> Geoffrey Broadwell wrote:
> > On Wed, 2008-01-16 at 22:38 -0700, Paul Seamons wrote:
> >>> I am starting to implement a GLUT and OpenGL binding for Parrot.
> [...]
> > I don't often get concentrated time
> > to help out with Parrot and Perl
Geoffrey Broadwell wrote:
On Wed, 2008-01-16 at 22:38 -0700, Paul Seamons wrote:
I am starting to implement a GLUT and OpenGL binding for Parrot.
[...]
I don't often get concentrated time
to help out with Parrot and Perl 6, but I have some now. If this is
going to be blocked indefinitely, my
On Jan 18, 2008 7:39 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> Note: Application of the patch attached entails a change in behavior.
> It will no longer be possible to say:
>
> svn update
> perl Configure.pl
> svn update (assuming a new revision number is displayed)
> make
>
> .
On Wed Sep 12 17:50:04 2007, [EMAIL PROTECTED] wrote:
> On Sat May 05 10:05:58 2007, [EMAIL PROTECTED] wrote:
> > On Sat May 05 10:04:24 2007, jkeen at verizon.net wrote:
> > > Patch applied in r18427 May 05 2007.
> >
> > I'm leaving the ticket open in the hope that some project member who
> > us
The patch attached refactors lib/Parrot/Revision.pm and all the files
that use it directly or indirectly.
On Tue Jan 15 09:31:18 2008, [EMAIL PROTECTED] wrote:
> Having looked a bit more at Parrot::Revision and the instances where it
> is used, I *think* we can make it go away completely, at leas
>
> When using a non-default C compiler, you will usually need to add a
> --link to the Configure line. So, something like...
>
> Configure.pl --cc=bcc32 --link=bcc32
>
Doesn't appear to make any difference.
--
Email and shopping with the feelgood factor!
55% of income to good causes. http
On Thu Jan 17 17:26:45 2008, [EMAIL PROTECTED] wrote:
> The following text shows the result of attempting to install Parrot
> using
> bcc32. The program appeared to hang at the "Generating CPU specific
> stuff"
> stage until killed.
>
> C:\parrot>Configure.pl --cc=bcc32
> Parrot Version 0.5.2 Conf
On Jan 17, 2008 5:26 PM, via RT arocker @ vex. net
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by [EMAIL PROTECTED]
> # Please include the string: [perl #49912]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=49912 >
>
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #49912]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49912 >
The following text shows the result of attempting to install Parrot using
bcc32. Th
Jerry Gay via RT wrote:
applied as r24965.
it's causing a heck of a lot of failing tests. however, i'll leave them
in for a day or three, while we see what we can do to get them passing.
hint: getting 'fudge' working on rakudo would do us a world of good.
~jerry
Do you mean running:
perl6
12 matches
Mail list logo
