I've banged together a first attempt at a miniparrot- that is, something
that can be built on any ANSI C system without anything other than a
compiler.
Right now, as a proof of concept, it's building a source tree and a shell
script which would build miniparrot under gcc. A real version woul
On Tue, 29 Oct 2002, Andy Dougherty wrote:
> On Tue, 29 Oct 2002, Andy Dougherty wrote:
>
> > Here's my proposal for stage one: This patch is intended to define
> > explicitly what the different compiler and linker commands and flags
> > are, what they are supposed to mean, and how they are to b
> -Original Message-
> From: Leopold Toetsch [mailto:lt@;toetsch.at]
>
> WRT your comment: "should we use a List * here", I slightly vote for
> yes. In the long run we could use List as the basic store for registers
> and stacks as well.
> List would only need a small extension to manage ar
The packfile contains for string constants the STRING internal field
"flags". This is used for various *internal* purposes, e.g. defining
that a string is external or COWed.
So a badly (i.e. non NULL) set flags field could seriously damage
parrots operation WRT strings.
IMHO, this field doesn't
Jonathan Sillito (via RT) wrote:
# New Ticket Created by Jonathan Sillito
# Please include the string: [perl #18170]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18170 >
- changed: sub.c
Comments?
WRT your comment:
