At 10:14 PM 11/22/2003 -0500, Melvin Smith wrote:
At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> to override it, it is not supported to choose INTVAL > OPCODE, though
> the inverse is. So storing it in the header is probably redundant, unless
> we cha
At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> Parrot currently assumes INTVAL size == OPCODE size because
> both get configured as the same integral type, although you can choose
> to override it, it is not supported to choose INTVAL > OPCODE, thoug
From: "Leopold Toetsch" <[EMAIL PROTECTED]>
> Jonathan Worthington wrote:
>
> > Hi,
> >
> > I've attached an example of calling a Win32 API using NCI.
>
> Could you please rework it to use the .pcc_begin/.nci_call interface (s.
> library/libpcre.imc for an example)
Done and attached.
Jonatha
Melvin Smith <[EMAIL PROTECTED]> wrote:
> Parrot currently assumes INTVAL size == OPCODE size because
> both get configured as the same integral type, although you can choose
> to override it, it is not supported to choose INTVAL > OPCODE, though
> the inverse is. So storing it in the header is pr
All~
We could try to keep the opcode count down by simply having a seed
opcode and an opcode to produce n random bytes... Anyone who wants more
specific ranges could do the modulus and addition themselves.
Matt
Leopold Toetsch wrote:
Almost forgotten about that, but I've checked in some days
At 03:18 PM 11/21/2003 -0500, Dan Sugalski wrote:
These could use some documenting (and yes, I know the answer to many) for
future use for folks generating PIR. (Hint, hint -- documentation is a
good thing)
I will make an attempt at answering all of these regarding how it is today,
as opposed to ho
At 12:13 PM 11/22/2003 +, you wrote:
* write intval size into PBC header
Leo, I know this is a first cut at freeze/thaw, and I'm happy you've
done it. Let me make some comments to you and Dan.
I'm pretty sure Dan and I discussed this when I was reworking bytecode
to be portable last year, but
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> Only a few fixes in imcc are needed to compile warning-free, most of
> them are unused parameters and variables.
Applied. Thanks,
> bye
> b=F6
leo
Dan Sugalski wrote:
These could use some documenting (and yes, I know the answer to many) for
future use for folks generating PIR. (Hint, hint -- documentation is a
good thing)
*) How do I declare an externally visible subroutine?
*) How do I store a global variable
*) How do I load a global vari
Jonathan Worthington <[EMAIL PROTECTED]> wrote:
> In the spirit of this, I attach a couple of patches that clear up some of
> the many warnings on Win32.
Thanks, applied.
> Jonathan
leo
10 matches
Mail list logo