Newsgroups: perl.perl6.internals
Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!nntp.perl.org
Return-Path: <brent...@cpan.org>
Mailing-List: contact perl6-internals-h...@perl.org; run by ezmlm
Delivered-To: mailing list perl6-intern...@perl.org
To: "'Dan Sugalski'" <d...@sidhe.org>,	<perl6-intern...@perl.org>
Subject: RE: Bytecode metadata
Date: Thu, 23 Jan 2003 00:10:29 -0800
Message-ID: <00a901c2c2b6$e4caaf40$7b01a8c0@deepblue>
MIME-Version: 1.0
Content-Type: text/plain;	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
In-Reply-To: <a05200f01ba5492b60e51@[192.168.2.1]>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-SMTPD: qpsmtpd/0.20, http://develooper.com/code/qpsmtpd/
Approved: n...@nntp.perl.org
From: brent...@cpan.org (Brent Dax)
References: <a05200f01ba5492b60e51@[192.168.2.1]>
Lines: 24

Dan Sugalski:
# Since it looks like it's time to extend the packfile format and the=20
# in-memory bytecode layout, this would be the time to start discussing=20
# metadata. What sorts of metadata do people think are useful to have=20
# in either the packfile (on disk) or in the bytecode (in memory).

I do think that, whatever "native" (i.e. understood by Parrot) metadata
we support, we *must* allow for extensibility, both for future native
metadata and for third-party tools.  Moreover, this must not be
implemented with a special type of metadata block, or by using
sequentially-increasing numbers.  (The first means that any metadata we
decide to add in the future will be slower than the metadata we add now;
the second has problems with several third-party tools picking the same
number.)

--Brent Dax <brent...@cpan.org>
@roles=3Dmap {"Parrot $_"} qw(embedding regexen Configure)

>How do you "test" this 'God' to "prove" it is who it says it is?
"If you're God, you know exactly what it would take to convince me. Do
that."
    --Marc Fleury on alt.atheism