On Wed, 25 Apr 2007 10:12:18 -0700
Allison Randal <[EMAIL PROTECTED]> wrote:
> Nikolay Ananiev wrote:
>
> > Maybe we have to search harder for new ways to advertise Parrot to
> > other communities and get new developers and supporters to the
> > project.
>
> On that I completely agree, but as a s
Allison Randal wrote:
Nicholas Clark wrote:
I guess that the most obvious current thing that ties Parrot to the Perl
community is that Parrot requires a copy of Perl to bootstrap, and all
the
build tools are written in Perl 5.
This is slated to change before the 1.0 release.
Since Nove
could one of you take a look at this for me? i've started digging into
the pmc2c code, but it'll be a long while before i grok it. since you
two have an understanding of that code already, perhaps something will
jump out at you.
~jerry
-- Forwarded message --
From: jerry gay <[EM
On Thursday 26 April 2007 07:43, Steve Peters wrote:
> This patch continues with the void pointer cleanups needed for compiling
> Parrot with a C++ compiler. This patch finishes up most of the code
> outside of src/pmc, but includes a bit in there as well. Next step is to
> take on src/pmc, then
On Apr 26, 2007, at 8:28 AM, James E Keenan wrote:
Allison Randal wrote:
Nicholas Clark wrote:
I guess that the most obvious current thing that ties Parrot to the
Perl
community is that Parrot requires a copy of Perl to bootstrap, and
all the
build tools are written in Perl 5.
This is sl
Does anyone understand the 'dummy' element in
include/parrot/stacks.h? Here is the relevant snippet:
typedef struct Stack_Chunk {
pobj_t obj;
int size;
const char * name;
struct Stack_Chunk *prev;
#if ! DISABLE_GC_DEBUG && defined(I386)
void * dumm
James E Keenan wrote:
Since November I've been working on maintaining those of Parrot's
configuration and build tools written in Perl 5. Lately I've been
trying to recruit others to help in that process. The discussion in
this thread suggests that at some future point some or all of the Per
Am Donnerstag, 26. April 2007 16:43 schrieb Steve Peters:
> - long * const out_array = mem_sys_allocate((sizeof (long)) * (arraylen
> + 1)); + long * const out_array = (long *)mem_sys_allocate((sizeof
> (long)) * (arraylen + 1));
I don't understand the rational for such patches nor the mem_a
Am Donnerstag, 26. April 2007 21:44 schrieb Andy Dougherty:
> Does anyone understand the 'dummy' element in
> include/parrot/stacks.h? Here is the relevant snippet:
>
> typedef struct Stack_Chunk {
> pobj_t obj;
> int size;
> const char * name;
> struct Stack_Ch
On 4/26/07, Matt Diephouse via RT <[EMAIL PROTECTED]> wrote:
First, the test (rearranged to include only the relevant parts):
+.sub main :main
+.local string ok, not_ok
+ok = "ok"
+not_ok = "not ok"
+
+# if 'not ok' is printed, it means that the lexical environment
+# for th
On Mon Apr 16 13:07:22 2007, [EMAIL PROTECTED] wrote:
> Without this patch, for runtime/parrot/library/config.pir to work, parrot
> has to be run in its root directory (in fact, there was an XXX note in there
> saying so.)
>
> I changed Parrot_get_runtime_prefix not to return a const value because
On Thursday 26 April 2007 13:12, Leopold Toetsch wrote:
> Am Donnerstag, 26. April 2007 16:43 schrieb Steve Peters:
> > - long * const out_array = mem_sys_allocate((sizeof (long)) *
> > (arraylen + 1)); + long * const out_array = (long
> > *)mem_sys_allocate((sizeof (long)) * (arraylen + 1)
12 matches
Mail list logo
