>>
>>I am very confused. THIS IS WHAT WE ALL SEEM TO BE SAYING. BITOPS ONLY
>>ON EIGHT-BIT DATA. AM I WRONG?
>
>
> No, it's not, and could you please not get emotional about this? It's
I apologize for using UPPERCASE. My only excuse is that it was not
personally aimed at you: I have been gri
Arthur Bergman <[EMAIL PROTECTED]> wrote:
> ... The obvious answer
> seems to be to have the embedding interface set the top of stack in
> each embedding function if it is not set. This would do the right thing
> and make it easy to embed parrot.
No. I've posted already this example:
{
PM
Arthur Bergman <[EMAIL PROTECTED]> wrote:
> All I want to do is.
> 1) create a parrot interpreter
> 2) create some pmcs
> 3) call some code inside parrot with those pmcs
I've now added a missing init function that sets the stack top:
Parrot_init_stacktop(Interp*, void*);
This function can be
On 2 May 2004, at 10:54, Leopold Toetsch wrote:
Arthur Bergman <[EMAIL PROTECTED]> wrote:
... The obvious answer
seems to be to have the embedding interface set the top of stack in
each embedding function if it is not set. This would do the right
thing
and make it easy to embed parrot.
No. I've
On 2 May 2004, at 11:47, Leopold Toetsch wrote:
All I want to do is.
1) create a parrot interpreter
2) create some pmcs
3) call some code inside parrot with those pmcs
I've now added a missing init function that sets the stack top:
Parrot_init_stacktop(Interp*, void*);
This function can be u
Arthur Bergman <[EMAIL PROTECTED]> wrote:
> On 2 May 2004, at 11:47, Leopold Toetsch wrote:
>> Parrot_init_stacktop(Interp*, void*);
>>
>> This function can be used as a replacement for Parrot_init(). I hope
>> that simplifies step 1)
> No, it entirely misses the point, every time I call into
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> link needs to be told that libnci.def is a module definition file, via
> the -def: flag. The patch changes libnci.def to -def:libnci.def.
Thanks, applied.
leo
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> PerlNum.get_string() should print "-0.00" for the value -0.0, but
> prints "0.00" on win32. get_string() now prints the sign symbol
> itself, instead of relying on sn?printf.
I'm not sure, if we shouldn't just one routine (string_from_num()) OTOH
Hi,
it seems as if the ICU makefiles don't work that well with BSD style makes
like the one in OpenBSD core and NetBSD. As I'm no makefile expert it's quite
hard for me to fix this, don't know if it is possible in a platform
independent manner.
The first bunch of errors is:
make: "/usr/tmp/pa
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Well... about that. It's actually easily doable with a bit of
> trickery. We can either:
I have trickery number 4) here. Dunno if its doable, but worth
considering IMHO:
Here is mmd.pasm (using bxor but substitute any math/bitwise/... op).
Comments inline
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> # recompile each bxor_p_p_p
> mmdvtfind P20, .VTABLE_BXOR, .PerlInt, .PerlInt
^^
This has to use the dynamic type of the PMC of course.
typeof I20, P17
typeof I21, P18
mmdvtfind P20,
>>> Jeff Clites <[EMAIL PROTECTED]> 2004-05-01 18:23:02 >>>
[Finishing this discussion on p6i, since it began here.]
> Good point. However, the more general usage seems to have largely
> fallen out of use (to the extent to which I'd forgotten about it
until
> now). For instance, the Java String c
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #29310]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29310 >
Add required symbols for export.
libnci.def
Flush buffers to avoid unordered output
# New Ticket Created by Will Coleda
# Please include the string: [perl #29309]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29309 >
This causes the example Makefile to be autogen'd.
? config/gen/makefiles/tcl_example
Two more things to keep in mind:
On May 1, 2004, at 4:54 PM, Aaron Sherman wrote:
If Perl defaults to UTF-8
People need to realize also that although UTF-8 is a pretty good
interchange format, it's a really bad in-memory representation. This is
for at least 2 related reasons: (1) To get to the
On May 2, 2004, at 7:38 AM, Andrew E Switala wrote:
Jeff Clites <[EMAIL PROTECTED]> 2004-05-01 18:23:02 >>>
[Finishing this discussion on p6i, since it began here.]
Good point. However, the more general usage seems to have largely
fallen out of use (to the extent to which I'd forgotten about it
un
On 2 May 2004, at 12:37, Leopold Toetsch wrote:
that simplifies step 1)
No, it entirely misses the point, every time I call into parrot the
place I called parrot_init_stacktop might not, or most likely will not
be in my current stack.
Can't you call that somewhere in an outer frame? E.g. where yo
At 4:00 PM +0200 5/2/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
Well... about that. It's actually easily doable with a bit of
trickery. We can either:
I have trickery number 4) here. Dunno if its doable, but worth
considering IMHO:
It's doable but the problem you run into
# New Ticket Created by Philip Taylor
# Please include the string: [perl #29315]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29315 >
Some changes so that "perl Configure.pl --cc=icl" correctly uses
the Intel C++ Co
19 matches
Mail list logo
