On Mon, Sep 02, 2002 at 09:49:25PM +0200, Leopold Toetsch wrote:
>
> This should be - from my (imcc) POV - reflected by these IN/OUT settings:
>
> op set(in PMC, in INT)
> op set(in PMC, in STR)
> op set(in PMC, in NUM)
> op set(out PMC, in PMC) # ok, $1 points to $2 now
Thinking
Sean O'Rourke wrote:
> On Mon, 2 Sep 2002, Dan Sugalski wrote:
>... I think it ends up being two more ops if you say "chop X
> entries" -- "getdepth; subtract; chop" vs. "setdepth".
Think the perlish way: chop -X could do it. Leave X or keep it.
BTW what is the difference between the rx_sta
Andy Dougherty (via RT) wrote:
> + op_load_lib("core", PARROT_MAJOR_VERSION,
> + PARROT_MINOR_VERSION,
> + PARROT_PATCH_VERSION);
Thanks for this one.
I did integrate it in my tree.
A _big_ imcc patch is in my queue and will be
On Mon, 2 Sep 2002, Nicholas Clark wrote:
> *) Careful elimination of all compiler warnings, particularly on non x86
>platforms, and for builds with non-default INTVAL size
I agree here. There are still *lots* of warnings. I've slowly whittled
away at them, but there are lots to go. Fixin
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #16941]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16941 >
The following patch changes the build system to use pre-generated files
for languages
On Mon, Sep 02, 2002 at 11:15:17AM -0700, Steve Fink wrote:
> On Mon, Sep 02, 2002 at 08:25:30AM -0700, Sean O'Rourke wrote:
> > On Mon, 2 Sep 2002, Dan Sugalski wrote:
> >
> > > Here's a call for potential goals for the 0.0.9 release of parrot. My list:
> > >
> > > *) Exceptions
> > > *) initial
I think those are necessary operations -- if you're going to use the
intstack in the first place. And personally, I don't intend to. I
think it's much easier to deal with a separate data structure than
something tied into the interpreter struct. A free-floating intstack,
if you will. But this has
Hi all,
I would like to discuss the intended meaning of ARGDIR_IN/OUT in
core.ops (core_ops.c).
s. also #16838 and #16895
imcc uses the IN/OUT information for determining the life status of a
symbol, which is the base for register allocation, so it's crucial.
The meaning in imcc is like:
IN
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #16938]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16938 >
imcc doesn't work anymore now that the version number has changed from 7
to 8. This
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #16937]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16937 >
This is a resubmit. Configure currently hard-wires ld_shared to a
GNU-binutils-speci
On Mon, Sep 02, 2002 at 01:33:45PM +0200, Aldo Calpini wrote:
> INTVAL iterator_sizeof()
> void iterator_reset()
> void iterator_set(void *data)
> void iterator_get(void *data)
> PMC* iterator_get_current()
> void iterator_next();
What is the advantage of having the aggregat
On Mon, 2 Sep 2002, Dan Sugalski wrote:
> At 3:59 PM + 9/2/02, "Sean O'Rourke" (via RT) wrote:
> >rx_stackdepth Ix -- Store the size of the regex stack in Ix
>
> Make that intstackdepth, since it's a general-purpose stack.
If so, we'll probably also want to change rx_clearstack and rx_initst
On Sun, Sep 01, 2002 at 02:30:35AM -0400, Mike Lambert wrote:
> > Small cleanups, but also a piece of my attempted fixes to the
> > BUFFER_external_FLAG. (The CVS version currently doesn't work anyway,
> > so don't worry about only getting parts of my fixes in; nothing
> > depends on it.)
>
> I'm
On Sun, Sep 01, 2002 at 02:32:26AM -0400, Mike Lambert wrote:
> Mr. Nobody wrote:
>
> > Date: Fri, 30 Aug 2002 18:13:27 -0700 (PDT)
> > From: Mr. Nobody <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: [PATCH] in makefile, move libparrot.a from "test" to "all"
> >
> > libparrot.a is not
At 3:59 PM + 9/2/02, "Sean O'Rourke" (via RT) wrote:
>rx_stackdepth Ix -- Store the size of the regex stack in Ix
Make that intstackdepth, since it's a general-purpose stack.
>rx_stackchop Ix -- shorten the regex stack to have Ix entries
Yeek--that's from the wrong end. We need to chop entr
On Mon, Sep 02, 2002 at 08:25:30AM -0700, Sean O'Rourke wrote:
> On Mon, 2 Sep 2002, Dan Sugalski wrote:
>
> > Here's a call for potential goals for the 0.0.9 release of parrot. My list:
> >
> > *) Exceptions
> > *) initial PMC freeze/thaw API
> > *) Sub indicators in bytecode
> > *) On-the-fly b
On Fri, 30 Aug 2002, Steve Fink wrote:
> On Fri, Aug 30, 2002 at 03:49:07PM -0400, Andy Dougherty wrote:
> > Thus what I'd really like to do here is generate two different makefile
> > fragments, depending on whether or not the user is using bison or (yacc or
> > byacc). With the current substit
# New Ticket Created by "Sean O'Rourke"
# Please include the string: [perl #16935]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16935 >
This adds the following two regex ops:
rx_stackdepth Ix -- Store the size of the re
Edit distance is a measure of the number of edits required to
turn one string into another, basically the size of a
character-by-character "diff". For example, the edit distance
between "aches" and "access" is one change and one insert:
aches
acCes
accesS
Depending on how you define the costs o
On Mon, 2 Sep 2002, Dan Sugalski wrote:
> Here's a call for potential goals for the 0.0.9 release of parrot. My list:
>
> *) Exceptions
> *) initial PMC freeze/thaw API
> *) Sub indicators in bytecode
> *) On-the-fly bytecode section generation
*) methods (in PASM and C)
*) implementation of som
On 2 Sep 2002, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
> Tom Hughes <[EMAIL PROTECTED]> wrote:
>
> > That explains why you are not seeing the last component. You are also
> > missing the first one for some reason. The most likely cause would be
> > that you have already used
In message <[EMAIL PROTECTED]>
Tom Hughes <[EMAIL PROTECTED]> wrote:
> That explains why you are not seeing the last component. You are also
> missing the first one for some reason. The most likely cause would be
> that you have already used key_next to discard the first component
> befor
On 2 Sep 2002, Tom Hughes wrote:
> This loop stops as soon as key_next() becomes NULL which means that
> you never process the last key component. I would guess that you want
> to make the first line into this:
>
> while (key != NULL) {
what can i say. OOPS :-)
/j
In message <[EMAIL PROTECTED]>
Josef Hook <[EMAIL PROTECTED]> wrote:
> As you can see above the while loop in multiarray below only iterates
> 4 times when it should iterate 6 times ( .MultiArray[2;3;2;1;1;1] ).
> The same happens when i define a 3 dim array .MultiArray[2;2;2]
> it only i
I've discovered a "feature" when using the new key implementation.
It seems that key_next function dosent walk down the chain of keyes like
the old key->next pointer did.
I've managed to reproduce this behaviour many times.
Consider this pasm code:
new P0, .MultiArray[2;3;2;1;1;1]
# New Ticket Created by Josef Höök
# Please include the string: [perl #16934]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16934 >
Added 2 new opses into core.ops that handles this code:
new P0, .MultiArray[2;
# New Ticket Created by Josef Höök
# Please include the string: [perl #16933]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16933 >
Added a new pmc function that is used for passing inital sizes to pmcs.
There was an old
# New Ticket Created by System Attendant
# Please include the string: [perl #16932]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16932 >
ScanMail for Microsoft Exchange has blocked a file attachment(s).
Place = [EMAIL P
# New Ticket Created by Josef Höök
# Please include the string: [perl #16931]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16931 >
Some minor updates on multiarray
/josef
-- attachment 1
Here's a call for potential goals for the 0.0.9 release of parrot. My list:
*) Exceptions
*) initial PMC freeze/thaw API
*) Sub indicators in bytecode
*) On-the-fly bytecode section generation
Anyone got any others? We can get the list together and then
prioritize from there.
--
Mattia Barbon wrote:
>> set P1, P0 # tells P1 that he's going to iterate P0
>
> This looks like a kludge. IMHO the correct way of getting an iterator
> is having the aggregate return it (say, using find_method/invoke);
that's a correct assumption, and when find_method/invoke will be
i
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #16926]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16926 >
Hi,
these static functions are
- never used
- produce ugly warnings with -Wall, whi
32 matches
Mail list logo
