I should have said there was no I PIR syntax help =-). I found a test for
C<.flatten_arg> after I saw it on the list, but it wasn't in the IMCC docs. That would have
saved me some time...
(That wording, btw, wasn't in there when I wrote my version. Must have missed a sync)
I'm an edge case becaus
William Coleda wrote:
I think it's worth mentioning C<.flatten_arg> in the first answer, and
the wording of the second answer needs a bit more explanation, perhaps:
Added a C<.flatten_arg> examples as well as your C snippets from
the previous mail.
Thanks,
leo
Will Coleda <[EMAIL PROTECTED]> wrote:
> Brings tcl's makefile in line with recent changes.
> +lib/tcllib.imc \
Only that line was missing?!
leo
I've added a test for AIO to the config system. You can watch this
config step by running:
perl Configure.pl ... --verbose-step=AIO
I don't know, how linux-specific it is. Success/failure reports and
patches for other posixish platforms welcome.
leo
On May-30, Leopold Toetsch wrote:
> Steve Fink <[EMAIL PROTECTED]> wrote:
>
> > Anyone mind if I commit this?
>
> The patch is fine.
>
> > ... One thing I'm not sure of, though -- I
> > try to behave myself and use Parrot_getenv rather than a plain
> > getenv(), but I'm not convinced the API is
The Perl6 compiler often appends on array onto another. Right now, it
does this by iterating over the source array. I would like to just use
the C op, but I am now getting a mixture of PerlArrays (from
Perl6) and Arrays (from C), and the C vtable entry
only works if the types of the arrays is ident
At 10:23 PM +0200 5/29/04, Stéphane Payrard wrote:
You are considering read-ony PMC versus others. Another issue
is properties. Many PMCs "classes" will support properties that will
alter their behavior. But most PMC instances will have no property
attached to them. Or just default values of them
At 11:55 AM +0200 5/30/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
We need the ability to layer PMCs. Nothing new, we need something of
the sort for transparent read-only-ness and probably thread-safety
What about the current implementation [1]:
Leo, you're missing the poin
On Sat, May 29, 2004 at 11:03:12PM -0700, Steve Fink wrote:
> +/* DEFAULT_ICU_DATA_DIR is configured at build time, or it may be
> + set through the $ICU_DATA_DIR environment variable. Need a way
> + to specify this via the command line as well. */
> +data_dir = Parrot_getenv("
On May-31, Nicholas Clark wrote:
> On Sat, May 29, 2004 at 11:03:12PM -0700, Steve Fink wrote:
>
> > +/* DEFAULT_ICU_DATA_DIR is configured at build time, or it may be
> > + set through the $ICU_DATA_DIR environment variable. Need a way
> > + to specify this via the command line as
Leopold Toetsch wrote:
Combinatorial explosion. This already requires four variants (normal,
const, threadsafe, const threadsafe), and we haven't even seen what real
users will want to do with PMCs yet.
Not quite. A const PMC is already thread-safe.
Hmm, good point. (I guess you can't set propert
On Mon, 2004-05-31 at 21:26, Brent 'Dax' Royal-Gordon wrote:
> Can this be done with special subclasses? Sure. But if we do it with a
> true layering system, we get an incredible amount of power essentially
> for free.
That sounds suspiciously like Perl 6 roles.
-- c
Hello everybody,
I'm about to learn myself perl6 (after using perl5 for some time).
One of my first questions deals with regexes.
I'd like to parse data of the form
Len: 15\n
(15 bytes data)\n
Len: 5\n
(5 bytes data)\n
\n
OtherTag: some value here
13 matches
Mail list logo
