James Michael DuPont wrote:
--- [EMAIL PROTECTED] wrote:
Mike --
Thats a lot of metadata.
OK that sounds fine. My current problems with the graphs of meta-data
are the speed of loading.
When you arrange the meta-data as a single opcode stream, you have ~zero
load time for the mmap()ed c
Nicholas Clark wrote:
The summary reminded me I had a question still
On Thu, Jan 30, 2003 at 08:42:34AM +0100, Leopold Toetsch wrote:
[ constant folding for eval ]
Create a hash table of values present at the time of the first eval, and
use that from then on?
There are 2 possibilities:
On Wed, 2003-01-29 at 05:02, Nicholas Clark wrote:
> Warning bells are ringing in my head. Someone sent code to p6i about 1 or
> 2 years ago that could convert between various floating point formats.
> You may be re-inventing wheels here.
>
> I forget who, and I've not managed to find it on googl
Hey Gopal,
Nice to meet you here ;)
--- Gopal V <[EMAIL PROTECTED]> wrote:
> If memory serves me right, James Michael DuPont wrote:
> > I just want to know how where we can put it. The Microsoft IL
> > has a whole section on meta-data,
>
> AFAIK, that just holds the offset, line number and file
The summary reminded me I had a question still
On Thu, Jan 30, 2003 at 08:42:34AM +0100, Leopold Toetsch wrote:
> Nicholas Clark wrote:
> >If I understand you correctly, every time an eval happens, more code is
> >created, and that code's associated constants are appended to the constant
> >table
--- [EMAIL PROTECTED] wrote:
> Mike --
>
> Thats a lot of metadata. Sounds like maybe the metadata is primary
> and the bytecode is secondary, in which case perhaps what you
> really want is a (metadata) tree decorated with bytecode rather than
> a (bytecode) array decorated with metadata.
Fair
Simon Glover (via RT) wrote:
# New Ticket Created by Simon Glover
# Please include the string: [perl #20707]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=20707 >
A fresh check-out of parrot from CVS is giving me a huge
The Perl 6 Summary for the week ending 20030202
Welcome to the second Perl 6 summary of the Copious Free Time era and
already I've broken the 'mailed out by Monday evening' promise. There
were reasons however, mostly to do with going down to London to do the
paperwork for my redunda
If memory serves me right, James Michael DuPont wrote:
> I just want to know how where we can put it. The Microsoft IL
> has a whole section on meta-data,
AFAIK, that just holds the offset, line number and filename. IIRC the
JVM had a LineNumberTable and VarNameTable for debugging which were
dec
# New Ticket Created by Simon Glover
# Please include the string: [perl #20707]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=20707 >
A fresh check-out of parrot from CVS is giving me a huge number of
failing tests:
Fa
> "PH" == Phil Hassey <[EMAIL PROTECTED]> writes:
PH> 1. Function case -- some languages like php don't use case for
PH> function or method names. Thus $a->toString(); is the same as
PH> $a->tostring(); However, a language like java does care. How will
PH> php be able to call the co
List,
I've been lurking here for about two months, after having read the summaries
for several months previous. I'm interested in parrot because 1. I want it
very badly for php / python / perl combinationability(?) 2. Just reading
about the project is a fascinating learning experience.
I've
Gregor,
It looks like we are going into a similar direction. I would like to
make sure that we can represent this information in the parrot, if the
compiler writers want to provide it.
--- [EMAIL PROTECTED] wrote:
> James --
>
> I'm open to other ideas. I've toyed with learning DAML and RDF for
Juergen,
I completly agree with you. For my needs, the meta-data does not have
to be loaded at the same time at all. I can be in a different file for
I care. I just want to know how where we can put it. The Microsoft IL
has a whole section on meta-data, and one wonders what Parrot might be
doing t
b. --
I agree that under normal circumstances the bytecode is primary.
I was observing that as more and more metadata is considered,
eventually its quantity (measured, say, in bytes) could approach
or even exceed that of the raw bytecode. In cases where one
would feel such a quantity of metadata i
[EMAIL PROTECTED] writes:
> Mike --
>
> Thats a lot of metadata. Sounds like maybe the metadata is primary
> and the bytecode is secondary, in which case perhaps what you
> really want is a (metadata) tree decorated with bytecode rather than
> a (bytecode) array decorated with metadata.
The byte
Mike --
Thats a lot of metadata. Sounds like maybe the metadata is primary
and the bytecode is secondary, in which case perhaps what you
really want is a (metadata) tree decorated with bytecode rather than
a (bytecode) array decorated with metadata.
Of course, the most natural candidate for the m
James Michael DuPont wrote:
Dear All,
I just wanted to ask about a conclusion on the bytecode metadata.
Here are the things I would like to know about a given bytecode :
what line (maybe column) it comes from
File/line information is already there (imcc -d -o...) and working.
If it is a me
Dear All,
I just wanted to ask about a conclusion on the bytecode metadata.
Here are the things I would like to know about a given bytecode :
what line (maybe column) it comes from
Possible comments about it.
If it is a method call, what is the method name,signature,locatoin
If it is a variable
19 matches
Mail list logo
