The infrastructure is now in place to test for character classes other
than is_digit. Character class functions may be specific to one class,
or generic; this split is controlled by the sequence of the enums in
chartype.h
Currently only is_digit has a dedicated function call slot, as this is
the o
At 10:11 AM 11/4/2003 -0500, Melvin Smith wrote:
At 03:18 PM 11/4/2003 +0100, Juergen Boemmels wrote:
* I needed many casts from PIOHANDLE to FILE * and vice versa. I'm not
sure if this one fits all approach of PIOHANDLE is the right way.
Maybe its better to make PIOHANDLE a union. But what to
On Tue, 4 Nov 2003, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > On Tue, 4 Nov 2003, Leopold Toetsch wrote:
>
> >> Are there already any plans for the frozen image data format?
> >> Currently I'm writing plain ASCII strings, which is quite handy for testing.
>
> > I'd prefe
Hey Juergen,
Here are a couple comments,
At 03:18 PM 11/4/2003 +0100, Juergen Boemmels wrote:
currently there is no (simple) way to open a file on an other layer
than the default layer. But this is necessary if we want to take
advantage from the layered approach.
So i added two new functions: pio
Thanks. 'bout time, I suppose, since even _I_ have stopped using
prd-perl6.pl...
/s
[EMAIL PROTECTED] (Joseph F . Ryan) writes:
> # New Ticket Created by Joseph F. Ryan
> # Please include the string: [perl #24403]
> # in the subject line of all future correspondence about this issue.
> # ht
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Tue, 4 Nov 2003, Leopold Toetsch wrote:
>> Are there already any plans for the frozen image data format?
>> Currently I'm writing plain ASCII strings, which is quite handy for testing.
> I'd prefer it to be as dense as possible.
Sure. The ASCII image
Hello,
currently there is no (simple) way to open a file on an other layer
than the default layer. But this is necessary if we want to take
advantage from the layered approach.
So i added two new functions: pio_open_with_layer and
pio_fdopen_with_layer which create IO-Objects on different layers.
On Tue, 4 Nov 2003, Melvin Smith wrote:
> At 08:32 AM 11/4/2003 +0100, Leopold Toetsch wrote:
> >Melvin Smith <[EMAIL PROTECTED]> wrote:
> >
> > > op invoke(STR, INT)
> > > PMC sub
> > > if($2 == 0) {
> > > sub = lookup $1
> > > $2 = sub # store the ref in the immediate data of the ins
On Tue, 4 Nov 2003, Leopold Toetsch wrote:
> Are there already any plans for the frozen image data format?
> Currently I'm writing plain ASCII strings, which is quite handy for testing.
I'd prefer it to be as dense as possible. Besides the format used in
bytecode files (so it'll take up memory sp
Melvin Smith <[EMAIL PROTECTED]> wrote:
> At 08:32 AM 11/4/2003 +0100, Leopold Toetsch wrote:
>>Melvin Smith <[EMAIL PROTECTED]> wrote:
>>
>> > $2 = sub # store the ref in the immediate data of the instruction
>>
>>This doesn't really work:
>>- byte-code is readonly, if mmap()ed and when ru
On Tue, 4 Nov 2003, Leopold Toetsch wrote:
> While implementing freeze/thaw I come - again - to this issue. Currently
> a HASH can store arbitrary and in one hash mixed items. This is done by
> storing an union with a type field.
> (List based) arrays on the other hand only have one fixed type per
Michael Carman said:
> On 10/31/2003 8:08 AM, Andy Lester wrote:
>>
>> Personally, I find the POD useful when I'm going thru a Devel::Cover run.
>> I interleave POD with functions and I like to refer to my docs.
>
> Well, since POD is intended to be documentation (not code or even comments)
> it
On Tue, Nov 04, 2003 at 07:18:34AM +0530, Abhijit Menon-Sen <[EMAIL PROTECTED]> wrote:
> At 2003-11-03 21:35:22 +, [EMAIL PROTECTED] wrote:
> >
> > > Just wondering, is keys() optimized for void context?
>
> Yes. From doop.c:Perl_do_kv:
>
> OP *
> Perl_do_kv(pTHX)
> { ...
>
>
On Mon, Nov 03, 2003 at 09:32:28PM -0600, Michael Carman wrote:
> On 11/3/2003 12:20 PM, Tim Bunce wrote:
> > On Tue, Oct 28, 2003 at 05:33:09PM +, [EMAIL PROTECTED] wrote:
> >>
> >> Right now, if your cover_db holds data for a dozen files, but you test them
> >> one at a time, you have to rea
At 2003-11-03 21:35:22 +, [EMAIL PROTECTED] wrote:
>
> > Just wondering, is keys() optimized for void context?
Yes. From doop.c:Perl_do_kv:
OP *
Perl_do_kv(pTHX)
{ ...
keys = hv;
(void)hv_iterinit(keys);/* always reset iterator regardless */
if (gim
# New Ticket Created by Joseph F. Ryan
# Please include the string: [perl #24403]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24403 >
Just a simple consistancy patch; as perl6 itself becomes more complex,
there is a grea
On Mon, Nov 03, 2003 at 05:06:01PM +0100, Elizabeth Mattijsen wrote:
> At 14:06 + 11/3/03, Tim Bunce wrote:
> >Its cheap to reset an iterator, just do
> > keys %foo;
> >before the C loop.
>
> Just wondering, is keys() optimized for void context? Perlfunc only states:
>
>As a side eff
> > I have noticed that docs\parrot_assembly.pod is old version of
> > \docs\pdds\pdd06_pasm.pod file.
> > Will these files be distinguished in the future?
>
> And they're both wrong, unfortunately. :( pdd06 is supposed to be
> canonical, so parrot_assembly.pod will be going away at some point. A
At 08:32 AM 11/4/2003 +0100, Leopold Toetsch wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> op invoke(STR, INT)
> PMC sub
> if($2 == 0) {
> sub = lookup $1
> $2 = sub # store the ref in the immediate data of the instruction
This doesn't really work:
- byte-code is readonly, if mmap()
Are there already any plans for the frozen image data format?
Currently I'm writing plain ASCII strings, which is quite handy for testing.
The Plan(tm) is to use PBC constant format (or extensions to this)
later, so that PMC constants nicely integrate into byte-code and that
freezing closures can
While implementing freeze/thaw I come - again - to this issue. Currently
a HASH can store arbitrary and in one hash mixed items. This is done by
storing an union with a type field.
(List based) arrays on the other hand only have one fixed type per
aggregate (e.g. ints for IntList or PMCs for Arr
Piers Cawley <[EMAIL PROTECTED]> wrote:
> Parrot Calling Convention Confusion
> ... -- I thought they were exactly the same as an unprototyped call,
> but you invoke the return continuation (P1) instead of P0, the other
> registers are set up exactly as if you were making an unprotot
Melvin Smith <[EMAIL PROTECTED]> wrote:
> op invoke(STR, INT)
> PMC sub
> if($2 == 0) {
> sub = lookup $1
> $2 = sub # store the ref in the immediate data of the instruction
This doesn't really work:
- byte-code is readonly, if mmap()ed and when running function core or
CGoto
- for
I would not suggest trying a current checkout until the aftermath
of tonight's patch is fixed. Most tests are passing but a select few
are broken. (Leo, hopefully you can quickly fix the pbc stuff that
is causing the others to fail)
The major change is that IMCC will now parse and collect all
compi
24 matches
Mail list logo
