At 11:51 PM +0530 11/6/02, Gopal V wrote:
If memory serves me right, Dan Sugalski wrote:
(Parrot bytecode is inherently unverifiable as well, at least in
the general case, which exacerbates the problem)
Hmm... Why ? ... Loose typing ?
Or does it just become an undecidability problem ?...
If memory serves me right, Dan Sugalski wrote:
> (Parrot bytecode is inherently unverifiable as well, at least in
> the general case, which exacerbates the problem)
Hmm... Why ? ... Loose typing ?
Or does it just become an undecidability problem ?...
Gopal
--
The difference between insanit
At 10:17 PM + 10/30/02, Kv Org wrote:
On Tue, 29 Oct 2002 09:55:23 -0800, Chromatic wrote:
I'd really like to be able to save comments from
source files as metadata. This has at least two
potential benefits. First, it >makes it much easier
to recreate the whole file from bytecode (especiall
On Tue, 29 Oct 2002 09:55:23 -0800, Chromatic wrote:
>
>I'd really like to be able to save comments from
>source files as metadata. This has at least two
>potential benefits. First, it >makes it much easier
>to recreate the whole file from bytecode (especially
>refactored bytecode).
>Second, it
On Monday 28 October 2002 13:02, Dan Sugalski wrote:
> At 1:08 PM -0800 10/27/02, chromatic wrote:
> >Is there an underlying function used to add arbitrary (Unicode text)
> > metadata to the bytecode?
> Arbitrary metadata? Nope, no plans for that. While I can see it as a
> useful thing (though i
At 8:40 AM -0800 10/28/02, chromatic wrote:
On Sunday 27 October 2002 23:27, Brent Dax wrote:
Appearances are deceiving--the first adds some (unparsed?) source code,
the second adds information on file and line numbers, probably based on
offset into the bytecode.
Similar in terms of impleme
On Sunday 27 October 2002 23:27, Brent Dax wrote:
> Appearances are deceiving--the first adds some (unparsed?) source code,
> the second adds information on file and line numbers, probably based on
> offset into the bytecode.
Similar in terms of implementation, that is. :) In Perl terms, I'd ex
At 1:21 PM +0100 10/28/02, Juergen Boemmels wrote:
I like the first one more: The data necessary to unpack a chunk is
localized in the first chunk (the DIRECTORY). Only this part of the
file needs to be read first. In the second case the metadata is
scattered over the whole file.
That's fine.
At 1:08 PM -0800 10/27/02, chromatic wrote:
On Sun, 27 Oct 2002 08:54:08 -0800, Dan Sugalski wrote:
These two seem highly similar:
=item Add source code to segment
This adds a line or more of source code to the bytecode segment.
=item Add line number information
This adds line number i
At 11:40 PM -0800 10/27/02, Brent Dax wrote:
Dan Sugalski:
# =item Add source code to segment
#
# This adds a line or more of source code to the bytecode segment.
Optional?
Yes.
# =item Add AST to segment
#
# This adds the AST for some of the source code to the bytecode segment.
Optional?
"Brent Dax" <[EMAIL PROTECTED]> writes:
[...]
> Optional?
>
> # =item Add bytecode to segment
> #
> # Add in actual bytecode to the segment.
>
> Not optional. :^)
really?
There may be reasons to have no bytecode. This segment could not be
run. This rises the question: If there are multiple se
Dan Sugalski:
# =item Add source code to segment
#
# This adds a line or more of source code to the bytecode segment.
Optional?
# =item Add AST to segment
#
# This adds the AST for some of the source code to the bytecode segment.
Optional?
# =item Add line number information
#
# This adds li
chromatic:
# On Sun, 27 Oct 2002 08:54:08 -0800, Dan Sugalski wrote:
#
# These two seem highly similar:
#
# > =item Add source code to segment
# >
# > This adds a line or more of source code to the bytecode segment.
#
# > =item Add line number information
# >
# > This adds line number info t
On Sun, 27 Oct 2002 08:54:08 -0800, Dan Sugalski wrote:
These two seem highly similar:
> =item Add source code to segment
>
> This adds a line or more of source code to the bytecode segment.
> =item Add line number information
>
> This adds line number info to the bytecode segment, allowing
At 6:34 PM + 10/27/02, Nicholas Clark wrote:
On Sun, Oct 27, 2002 at 11:54:08AM -0500, Dan Sugalski wrote:
The bytecode segments can hold more than just bytecode. They can also
hold the source that corresponds to the generated bytecode, the AST
for the source that corresponds to the genera
On Sun, Oct 27, 2002 at 11:54:08AM -0500, Dan Sugalski wrote:
> The bytecode segments can hold more than just bytecode. They can also
> hold the source that corresponds to the generated bytecode, the AST
> for the source that corresponds to the generated bytecode, the line
> number information for
Okay, here's a partial PDD on internal bytecode generation. This is
*very* sketchy--at the moment it's just an enumeration of the
functionality we'll need,as I see it.
Take a look at this, and see where things might be missing or
unclear. Once we've hashed out the desired functionality, I'll ro
17 matches
Mail list logo
