Leopold Toetsch writes:
Dan Sugalski [EMAIL PROTECTED] wrote:
At 4:54 PM -0500 2/25/04, Simon Glover wrote:
If I'm understanding the docs correctly, this should print '0'.
Instead, it prints 'Array index out of bounds!'
Another bug, though the offset ought to be 2 right now.
Goplat [EMAIL PROTECTED] wrote:
[ patches ]
Thanks, applied.
leo
Andrew Dougherty [EMAIL PROTECTED] wrote:
Solaris/SPARC/Sun cc, longsize=4:
# PackFile_unpack: Not a Parrot PackFile!
# Magic number was [0x20a54100] not [0x013155a1]
Does it work now?
And, just to round out the report, on x86 with long-long opcodes,
... is broken ;)
(what you
Leopold Toetsch [EMAIL PROTECTED] wrote:
Please help me fill out the blanks by sending or committing patches.
Please make sure to have the latest and best Parrot from CVS.
Still a lot of platforms missing. Please ...
:r PLATFORMS
Parrot-0.0.999 was reported to compile and run tests
docs/pdds/pdd15_objects.pod, =head2 Translation, includes (edited)
What .NET calls an attribute parrot calls a property
What .NET calls a property parrot calls an attribute
Ouch.
In these lines one hears the echos of future years of confusion,
endlessly repeated explanations, failed
At 2:21 PM -0500 2/25/04, Simon Glover wrote:
(You're probably getting sick of these by now...)
Should asking for a non-existant attribute cause Parrot to throw an
exception. Currently, it doesn't seem to be able to make up its mind
[snip]
but if we ask for an attribute with an offset = 2
or
[EMAIL PROTECTED] (Aaron Sherman) writes:
At the current rate, the aforementioned apoc #11 will be out sometime
after I die, a frustrated old man who remembers the glory days of Perl
3.
The current rate is not going to be sustained; the Perl 6 class sytem
is a massive thing, and once that's
At 8:10 AM +0100 2/26/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
At 4:54 PM -0500 2/25/04, Simon Glover wrote:
If I'm understanding the docs correctly, this should print '0'.
Instead, it prints 'Array index out of bounds!'
Another bug, though the offset ought to be 2
At 2:38 PM +0100 2/26/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
At 8:10 AM +0100 2/26/04, Leopold Toetsch wrote:
*Please* don't. Cclassoffset (and attribute access) should by all
means start with 0.
Why?
Simplifies compilers:
newclass P1, Foo
addattribute P1, i
Once we've got 0.1.0 put to bed we're going to need to move in on
0.1.1. I'd like to have three things concentrated on:
1) Proper constructors, destructors, fallback method searching, and
overloaded operator and assignment for objects
2) Namespaces all finalized
3) Runtime bytecode loading
At 10:03 AM -0500 2/26/04, Simon Glover wrote:
On Thu, 26 Feb 2004, Dan Sugalski wrote:
At 2:38 PM +0100 2/26/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
At 8:10 AM +0100 2/26/04, Leopold Toetsch wrote:
\No, it won't. No code should ever assume an absolute offset.
Dan Sugalski [EMAIL PROTECTED] wrote:
Yep, it looks like everything that should work now actually *does*
work now
I've committed some fixes and more tests. Dan, can you please have a
look at:
$ perl -Ilib t/pmc/objects.t
[ snip ]
ok 23 - attribute values and subclassing 2
and add some
At 6:22 PM +0100 2/26/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
Yep, it looks like everything that should work now actually *does*
work now
I've committed some fixes and more tests. Dan, can you please have a
look at:
$ perl -Ilib t/pmc/objects.t
[ snip ]
ok 23 - attribute
On 26 Feb 2004, at 18:57, Mitchell N Charity wrote:
A perl by any other name, may be a different perl.
perl and /usr/bin/perl are both common in #!'s.
I been changing them to #! perl -w when i find them, which is why
your list covers the places I haven't visited. The good thing about the
bang
At 9:19 PM +0100 2/26/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
At 6:22 PM +0100 2/26/04, Leopold Toetsch wrote:
- classoffset and attribute offsets of subclassed objects, e.g.
how to get at the very first attribute
Which very first attribute? The first attribute for a
Dan Sugalski writes:
At 2:38 PM +0100 2/26/04, Leopold Toetsch wrote:
Simplifies compilers:
newclass P1, Foo
addattribute P1, i
findclass I1, Foo
new P2, I1
classoffset I2, P2
In static cases, where P2 is known to be a CFoo, attrib #0 (i) would
be always 0. That
# New Ticket Created by Adam Thomason
# Please include the string: [perl #27167]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=27167
Attached patch adds docs/porting_intro.pod, a newcomer's guide to Parrot
On Thu, 26 Feb 2004 09:29:59 +0100, [EMAIL PROTECTED] (Leopold Toetsch) wrote:
Leopold Toetsch [EMAIL PROTECTED] wrote:
Please help me fill out the blanks by sending or committing patches.
Please make sure to have the latest and best Parrot from CVS.
Here (and attached) is summary of the
Dan Sugalski [EMAIL PROTECTED] wrote:
At 6:22 PM +0100 2/26/04, Leopold Toetsch wrote:
- classoffset and attribute offsets of subclassed objects, e.g.
how to get at the very first attribute
Which very first attribute? The first attribute for a class, or the
first attribute in the object?
Here's a summary of what I've been able to test so far. Feel free to
edit as you see fit. (The Solaris Y/84 means 84 subtests failed under
'make testj'. I had to manually kill a number of them too, so if you just
want to replace that by a plain 'No', it's ok by me.
Finally, it'd probably make
Some quick observations on parrot_2004-02-26_08.
Odd files to be executable:
./docs/dev/dod.dev
./docs/dev/rx.dev
./languages/tcl/MAINTAINER
./languages/tcl/examples/Makefile
./lib/Digest/Perl/MD5.pm
A perl by any other name, may be a different perl.
perl and /usr/bin/perl
On Thu, 26 Feb 2004, Dan Sugalski wrote:
At 10:03 AM -0500 2/26/04, Simon Glover wrote:
On Thu, 26 Feb 2004, Dan Sugalski wrote:
like t/pmc/objects.t?
I was waiting for you to pull that out. :) Yes, objects.t assumes
some evil low-level knowledge of the internals.
Well, in
Andrew Dougherty [EMAIL PROTECTED] wrote:
perl Configure.pl
will automatically pick up this broken configuration.
Yep. We have to cleanup here. Ages ago we did need a proper perl for
generating the pack formats. Now we just need any perl that runs the
config scripts. Parrot types
At 10:13 AM -0500 2/26/04, Andrew Dougherty wrote:
In a somewhat similar vein, a challenge is emerging on the
Linux/UltraSPARC front. Under Debian's current 'unstable' and 'testing'
distributions, for example, you end up with the following types:
iv=long, intvalsize=8, intsize=4,
On Thu, 26 Feb 2004, Leopold Toetsch wrote:
Andrew Dougherty [EMAIL PROTECTED] wrote:
Solaris/SPARC/Sun cc, longsize=4:
# PackFile_unpack: Not a Parrot PackFile!
# Magic number was [0x20a54100] not [0x013155a1]
Does it work now?
Yes, great! Thanks.
And, just to round out
On Thu, 26 Feb 2004, Dan Sugalski wrote:
At 2:38 PM +0100 2/26/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
At 8:10 AM +0100 2/26/04, Leopold Toetsch wrote:
*Please* don't. Cclassoffset (and attribute access) should by all
means start with 0.
Why?
Simplifies
Dan Sugalski [EMAIL PROTECTED] wrote:
At 8:10 AM +0100 2/26/04, Leopold Toetsch wrote:
*Please* don't. Cclassoffset (and attribute access) should by all
means start with 0.
Why?
Simplifies compilers:
newclass P1, Foo
addattribute P1, i
findclass I1, Foo
new P2, I1
Dan Sugalski [EMAIL PROTECTED] wrote:
The rule is that a method in a class has access to the attributes for
that class and nothing else.
Ah, that was the reason of my confusion. Could you adapt the docs
accordingly:
,--[ pdd15 ]---
| DESCRIPTION
On Thu, Feb 26, 2004 at 02:50:50PM -0500, Mark J. Reed wrote:
: chromatic With Apocalypse 12 (soon!)
: RobinBerjon how soon? :)
: LarryWall here's the rough outline
:
: [indicating that it's pretty soon indeed]
:
: Cool! But now I'm a little confused - what happened to Apocalypses 8
: through
On Thu, 2004-02-26 at 14:26, Larry Wall wrote:
ch26/011.cf Examples encoded with =also for|begin|end POD commands
ch26/044 Bring Documentation Closer To Whatever It Documents
ch26/065 Add change bar functionality to pod
ch26/079 The Predefined POD Streams are Cperl, Cdata,
On Thu, 2004-02-26 at 11:50, Mark J. Reed wrote:
Cool! But now I'm a little confused - what happened to Apocalypses 8
through 11? :)
They were:
- 8, References
- 9, Data Structures
- 10, Packages
- 11, Modules
Since 12, Objects is more important (and covers
2004-02-26T14:26:47 Larry Wall:
Well now, I remember Perl 0, sonny.
Does that still exist anywhere? I don't have anything older than
perl 1.
They don't make 'em like they used to...
That they don't. On Bent Linux (my own distro, based on uClibc
instead of glibc) I get
; ls -l perl1 perl5.8.1
[EMAIL PROTECTED] (Bennett Todd) writes:
2004-02-26T14:26:47 Larry Wall:
Well now, I remember Perl 0, sonny.
Does that still exist anywhere?
If nowhere else, Larry's got a copy IN HIS HEAD. :)
--
I have heard that the universe does not support atomic operations
(although I've not seen
SC == Simon Cozens [EMAIL PROTECTED] writes:
SC [EMAIL PROTECTED] (Bennett Todd) writes:
2004-02-26T14:26:47 Larry Wall:
Well now, I remember Perl 0, sonny.
Does that still exist anywhere?
SC If nowhere else, Larry's got a copy IN HIS HEAD. :)
better than a copy in his
On Thu, 2004-02-26 at 13:42, Simon Cozens wrote:
[EMAIL PROTECTED] (Larry Wall) writes:
It's the coherence that I can't delegate, and if I tried to, we would
certainly end up with Second System Syndrome Done Wrong, instead of Done
Right.
You know, it's statements like this that make it
[EMAIL PROTECTED] (Larry Wall) writes:
It's the coherence that I can't delegate, and if I tried to, we would
certainly end up with Second System Syndrome Done Wrong, instead of Done
Right.
You know, it's statements like this that make it hard for even me to
be curmudgeonly.
E7 is coming
chromatic With Apocalypse 12 (soon!)
RobinBerjon how soon? :)
LarryWall here's the rough outline
[indicating that it's pretty soon indeed]
Cool! But now I'm a little confused - what happened to Apocalypses 8
through 11? :)
-Mark
On Thu, Feb 26, 2004 at 12:31:04PM -0500, Aaron Sherman wrote:
: I cringe at what I'm about to ask because I know it's pushy, but thus is
: the burden of my impatience and hubris...
:
: There was a document:
:
: TITLE
: Apocalypse 1: The Ugly, the Bad, and the Good
:
On Thu, Feb 26, 2004 at 07:30:05PM +0100, Robin Berjon wrote:
: chromatic wrote:
: With Apocalypse 12 (soon!)
:
: I'm sorry but this just begs for the question: (vaguely) how soon? :)
Well, here's the rough outline. I still have to do some writing on
multiple dispatch, overloading, and
On Thu, 2004-02-26 at 12:57, Simon Cozens wrote:
1. Larry gets help in writing these (various degrees of delegation).
I think we've been through this idea, no?
I dropped off the face of the earth for a bit... sorry if I am
re-hashing something old I did not see anything in the archives, but
chromatic wrote:
With Apocalypse 12 (soon!)
I'm sorry but this just begs for the question: (vaguely) how soon? :)
I get all excited whenever I hear Perl and six in the same sentence,
and it's building up to be unbearable ;)
--
Robin Berjon
On Thu, 2004-02-26 at 09:31, Aaron Sherman wrote:
And in it Apocalypse #26 was mentioned. Above, Larry mentions #11. At
first the rate of 1 apolcalypse per month seemed to support the idea
that Perl 6 would be defined within the next couple of years. However,
trending shows that this function
On Tue, 2004-02-24 at 03:22, Larry Wall wrote:
[...] RFC 74 proposes the same thing. But I classified it under
Apocalypse 11, Modules, which we skipped over to get to Objects
first. So it hasn't actually been discussed much.
[...]
most exportation will be done simply by marking the routines
The Perl 6 Summary for the week ending 20040222
Welcome to the latest belated Perl 6 Summary. I'm running late, so we'll
just dive straight into perl6-internals
Loading bytecode at runtime
Last week Dan had specced out the rules for runtime loading of bytecode.
This week, Leo
44 matches
Mail list logo
