--- Jonadab the Unsightly One <[EMAIL PROTECTED]> wrote:
> "Jonadab the Unsightly One" <[EMAIL PROTECTED]> writes:
>
> > Does this imply, though, that it's pointing to specific elements,
>
> Wow, I wasn't paying attention to what I was thinking there.
> Obviously it points to specific elements,
"Jonadab the Unsightly One" <[EMAIL PROTECTED]> writes:
> Does this imply, though, that it's pointing to specific elements,
Wow, I wasn't paying attention to what I was thinking there.
Obviously it points to specific elements, because the subscripts used
to create a slice don't have to be sequen
David Storrs <[EMAIL PROTECTED]> writes:
> my $r_slice = [EMAIL PROTECTED];
> @$r_slice = qw/ a b c d e /;
> print @a; # 0 a b c d e 4 5
This seems right to me. It would take approximately no time to get
used to this semantic, IMO.
> # Note that it does NOT modify in r
IIRC, that has been the policy during previous freezes.
However, I can stop tinkering if its getting in anyone's
way or on anyone's nerves...
Regards,
-- Gregor
On Tue, 2003-07-08 at 18:01, Melvin Smith wrote:
> At 11:50 PM 7/8/2003 +0200, Leopold Toetsch wrote:
> >Gregor N. Purdy wrote:
> >
>
Melvin --
Thanks!
Its of only limited utility until I get the key stuff
working, but I was tired of having a null PMC story
for Jako.
Regards,
-- Gregor
On Tue, 2003-07-08 at 18:01, Melvin Smith wrote:
> At 05:44 PM 7/8/2003 -0400, Gregor N. Purdy wrote:
> >I just checked in a small patch tha
On Sun, Jul 06, 2003 at 01:02:12PM +0100, Fergal Daly wrote:
> [EMAIL PROTECTED]:> perl Makefile.PL
> Writing Makefile for Test::Deep
> You tried to run a test without a plan! Gotta have a plan. at
> /usr/lib/perl5/5.8.0/Test/NoWarnings.pm line 99
> END failed--call queue aborted.
> # Looks like
I think I've finally straightened my mail configuration out enough for
this to go somewhere. There is no feature freeze. That was just an old
message that was dug up accidentally from the past. I denied it
several times as soon as I saw it, which wasn't very soon because I
recently had a death in m
On Tue, Jul 01, 2003 at 09:09:34PM -0400, Dan Sugalski wrote:
> At 11:43 PM +0200 6/29/03, Leopold Toetsch wrote:
> >Dan Sugalski wrote:
> >[ stack implementations ]
> >
> >Well... we only really have three.
> >
> >Control, User & Pad have the same stack engine. The register backing
> >stacks and
On Mon, Jul 07, 2003 at 02:24:14PM +0200, Juergen Boemmels wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
> > Clinton Pierce <[EMAIL PROTECTED]> wrote:
> > >> Subject: Re: [ANNOUNCE] Parrot is feature-frozen until Wednesday
> >
> > I must somehow have missed this announce.
>
> Me too.
At 11:50 PM 7/8/2003 +0200, Leopold Toetsch wrote:
Gregor N. Purdy wrote:
All --
I just checked in a small patch that allows Jako to start
grokking PMCs. For example:
During feature freeze -
I think languages/ (besides imcc) should probably be
exempt of freezes unless Parrot depends on said l
At 05:44 PM 7/8/2003 -0400, Gregor N. Purdy wrote:
I just checked in a small patch that allows Jako to start
grokking PMCs. For example:
use sys;
var pmc foo;
foo = new PerlUndef;
foo = "Hello, world!\n";
sys::print(foo);
Neato, by the way.
-Melvin
Gregor N. Purdy wrote:
All --
I just checked in a small patch that allows Jako to start
grokking PMCs. For example:
During feature freeze -
SCNR
leo - what feature freeze;-) - is one?
Clinton Pierce wrote:
What I do know is that imcc -t under Win32 is crash-happy
Snippet runs fine on Linux (with typo adjusted or not) as well as your
previous one, -t or not.
But, as IO is under *construction* some issues might remain. They'll get
resolved.
leo
Juergen Boemmels wrote:
Leopold Toetsch <[EMAIL PROTECTED]> writes:
So during a DOD run the trails of an IO PMC are found on the system
stack during trace_mem_block. The main problem seems to be, that gcc
uses 16-byte aligned stack frames by default.
*Ouch* I spend the whole Friday searching th
All --
I just checked in a small patch that allows Jako to start
grokking PMCs. For example:
use sys;
var pmc foo;
foo = new PerlUndef;
foo = "Hello, world!\n";
sys::print(foo);
Regards,
-- Gregor
--
Gregor Purdy[EMAIL PROTE
On Tue, 8 Jul 2003, Nicholas Clark wrote:
> On Tue, Jul 08, 2003 at 06:48:02PM -, Simon Glover wrote:
> > cvsuser 03/07/08 11:48:02
> >
> > Modified:.debug.c
> > Log:
> > Add missing \ in multiline strings -- patch courtesy of <[EMAIL PROTECTED]>
>
> >"Delete a break
On Tue, Jul 08, 2003 at 06:48:02PM -, Simon Glover wrote:
> cvsuser 03/07/08 11:48:02
>
> Modified:.debug.c
> Log:
> Add missing \ in multiline strings -- patch courtesy of <[EMAIL PROTECTED]>
>"Delete a breakpoint.\n\n\
> -The breakpoint to delete must be specifie
Typo!
> getstderr P3 # STDOUT
Should have been "getstdout"
Although... if left at getstderr the error also goes away. (Add that to my bullet
list.) My haven't-grokked-the-code psychic abilities tell me that "getstdout" does
something Real Bad to the stdout filehandle
I'm not sure whether getstd\w+ is supposed to give me a new reference or not. From
now on I'll code that portion defensively.
What I do know is that imcc -t under Win32 is crash-happy and I can't trace beyond the
first getstdin. Greatly simplified example:
.sub _main
$P0=new PerlArray
Clinton Pierce wrote:
I suppose PMC authors (or opcode authors?) should be pretty clear on whether they're re-using the same PMC or cloning up a new one.
The semantics of PMC operations have to be better documented. "The Book"
has more examples on that.
But there are basically very simple and v
Clinton Pierce wrote:
Addendum: One more applies:
- Storing integral types in an Array/PerlArray creates a new PerlUndef
inside the array holding the value. This is currently different to
PerlHash's operation, which stores items as is. We should probably unite
these 2 to one kind of semantics.
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> I have a (partial?) solution for this. What AFAIK is going on is
> something like this:
>
> C-stack: Parrot_open() ... later ... do_dod_run()
>... ...
> $1 = pmc_new sub $0x44, %esp
>
On Tue, 8 Jul 2003, [EMAIL PROTECTED] (via RT) wrote:
> # New Ticket Created by [EMAIL PROTECTED]
> # Please include the string: [perl #22901]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=22901 >
>
> Multi-line string c
"Clinton Pierce" <[EMAIL PROTECTED]> writes:
> Given that, there's a possible bug in Jürgen's patch (or IMCC?). Given:
>
> .sub _main
> call _INIT
> .arg 0
> call _READLINE
> .result $S0
> print $S0
> end
> .end
> .sub _INIT
> $P0=new PerlArray # A
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #22901]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22901 >
Multi-line string constants require a \ at the end of each line to compile
correctl
> Yep a bug is here. But this bug is a BASIC compiler bug. Things that go
> into aggregates (or are stored in lex pads/global tables) are stored by
> reference. You have to clone PMCs to get independed vars:
Thanks for clearing this up. In my head I was confused between the difference in,
say,
Perl 6 Summary for the week ending 20030706
Welcome to this week's Perl 6 Summary, coming to you live from a
gatecrashed Speakers' lounge at OSCON/TPC, surrounded by all the cool
people like Dan Sugalski, Lisa Wolfisch, Graham Barr and Geoff Young,
who aren't distracting me from wri
Clinton Pierce wrote:
new $P4, PerlArray
A current workaround for the missing clone in ParrotIO:
getstdin P0
getstdout P1
getstderr P2
$P4[0], P0
$P4[1], P1
$P4[2], P2
leo
Clinton Pierce wrote:
set P1[0], P0
getstdout P0# <-- bug is here? Overwrote my P0.
set P1[1], P0
Yep a bug is here. But this bug is a BASIC compiler bug. Things that go
into aggregates (or are stored in lex pads/global tables) are stored by
reference. You
Simon Glover <[EMAIL PROTECTED]> wrote:
> I think the read & write ops in core.ops are obsolete as well;
> the patch below removes them.
Yep. Applied & thanks.
> Simon
leo
>>> .sub _main
>>> fdopen $P1, 0, "r" # STDIN
>
>BTW
> fdopen $P1, 0, "<" # read STDIN
>
>>> 3. its currently only defined for PIO_OS_UNIX
>
>> Okaaay, so the plan is for this to work and I should probably code this way anyway,
>> right?
>
> You could just
Back in.
On Tuesday 08 July 2003 11:32, Sean O'Rourke wrote:
> On 7 Jul 2003, Daniel Grunblatt wrote:
> > cvsuser 03/07/07 13:20:40
> >
> > Modified:jit/ppc jit_emit.h
> > Log:
> > * 2 instructions instead of 3 to load a 32 bit integer.
>
> I'm not sure this is a win, since loading
I think the read & write ops in core.ops are obsolete as well;
the patch below removes them.
Simon
--- core.ops.oldTue Jul 8 10:18:46 2003
+++ core.opsTue Jul 8 10:19:36 2003
@@ -86,7 +86,6 @@
=cut
-
=item B(out INT)
@@ -113,47 +112
JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
> Hello,
> The integer file descriptors are depreciated. In this two step patch
> they are removed from io.ops.
Thanks, applied plus some more cleanup in examples.
leo
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #22899]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22899 >
Hello,
The integer file descriptors are depreciated. In this two step patch
they are
35 matches
Mail list logo
