test_parrot -w (fixed)

Argh, I accidentally sent TWO patch.txt's. The one attached to THIS message is the right one. --Brent Dax [EMAIL PROTECTED] Parrot Configure pumpking and regex hacker Check out the Parrot FAQ: http://www.panix.com/~ziggy/parrot.html (no, it's not mine) . hawt sysadmin chx0rs This is sad.

Re: test_parrot -w (fixed)

Brent Dax: > Argh, I accidentally sent TWO patch.txt's. The one attached to THIS > message is the right one. Thanks, applied. Working on %P support for PMCs. -- "He was a modest, good-humored boy. It was Oxford that made him insufferable."

[PATCH misc.c] Fix up *some* of the warnings

Unfortunately I can't get the ones about argument 4 of gen_sprintf_call so easily :( --- misc.c~ Tue Feb 5 16:08:18 2002 +++ misc.c Tue Feb 5 16:47:38 2002 @@ -73,6 +73,12 @@ break;

Re: [PATCH misc.c] Fix up *some* of the warnings

Jonathan Stowe: > Unfortunately I can't get the ones about argument 4 of gen_sprintf_call so > easily :( Thanks, applied. -- "In matters of principle, stand like a rock; in matters of taste, swim with the current." -- Thomas Jefferson

Re: test_parrot -w

On Tue, Feb 05, 2002 at 01:06:25AM -0800, Brent Dax wrote: > This patch adds warnings capability to Parrot. It adds actual warnings > throughout the PerlUndef class, primarily to show how it's done. It > also adds a half-functional Parrot_sprintf() and friends. > > On the Parrot_sprintf: a goo

[PATCH] jit for solaris [APPLIED]

I've applied the following little patch which is required for those using Sun's assembler. It helps the make process a bit further along. I still get core dumps for test_parrot -j. It might have to do with my 64-bit perl, but I don't have time to investigate. This patch at least let the compila

[PATCH] misc.c: Remove //-style comments [APPLIED]

I've already applied the following little patch, necessary to allow compilation by a C compiler that doesn't support the // - style comments. diff -r -u parrot-orig/misc.c parrot-andy/misc.c --- parrot-orig/misc.c Tue Feb 5 09:04:13 2002 +++ parrot-andy/misc.c Tue Feb 5 12:01:39 2002 @@ -147

Parrot Trooper

I'd like to do a Parrot Trooper t-shirt or something along those lines. Maybe some of you guys have some cool theme we could use, but I'd like to do it like an award basis so when someone did something particularly noteworthy or applaudable (spelling?) for the cause we could stick one in the mail.

Re: Parrot directory structure

I think your suggestions sound pretty good to me.Personally, i'd lean towards possibility 2, since 1 is doable if you plan for 2, but not necessarily vice-versa. Otherwise I think your proposal sounds good. But then again i'm nobody ;) --Josh At 23:24 on 02/03/2002 GMT, [EMAIL PROTECTED

[PATCH] Nearly the last of the warnings.

This might spoil someones future plans but doesn't break anything existing AFAICT - apart from those pesky ones left in misc.c the only ones left should be from generated code which I have a plan for which I will share later :) Index: jit.c

Re: [PATCH] Nearly the last of the warnings.

Re: [PATCH] jit for solaris [APPLIED]

On Tue, Feb 05, 2002 at 02:10:15PM -0500, Andy Dougherty wrote: > I've applied the following little patch which is required for those using > Sun's assembler. It helps the make process a bit further along. > I still get core dumps for test_parrot -j. It might have to do > with my 64-bit perl, bu

Re: [PATCH] Nearly the last of the warnings.

On Tue, 5 Feb 2002, Melvin Smith wrote: >(I Wrote): > >diff -u -r1.12 jit.c > >--- jit.c 29 Jan 2002 14:05:31 - 1.12 > >+++ jit.c 5 Feb 2002 20:46:43 - > >@@ -214,7 +214,7 @@ > > address = (INTVAL *)&s->strlen; > > br

[PATCH] MinGW fix

* hints/mswin32.pl - move $c{platform} = win32 outside $is_msvc * Configure.pl - fixed jitarch/os detection for Win32 ( was using cpu = MSWin32, os = x86 ) Regards Mattia Index: Configure.pl === RCS file: /home/perlcvs/pa

Re: [PATCH] Nearly the last of the warnings.

On Tue, 5 Feb 2002, Jonathan Stowe wrote: > AFAICT - apart from those pesky ones left in misc.c the only ones left > should be from generated code which I have a plan for which I will share > later :) Well, those and the 86 cast increases required alignment of target type warnings we

Re: [PATCH] Nearly the last of the warnings.

On Tue, 5 Feb 2002, Andy Dougherty wrote: > On Tue, 5 Feb 2002, Jonathan Stowe wrote: > > > AFAICT - apart from those pesky ones left in misc.c the only ones left > > should be from generated code which I have a plan for which I will share > > later :) > > Well, those and the 86 > > cast inc

Re: [PATCH] Nearly the last of the warnings.

On Tue, Feb 05, 2002 at 05:19:07PM -0500, Andy Dougherty wrote: > Well, those and the 86 > > cast increases required alignment of target type > > warnings we still get all over the place on SPARC :-). Gah. You're winning. :-( There are only 79 of them on ARM. Nicholas Clark -- EMCFT ht

Re: [PATCH] Nearly the last of the warnings.

On Tue, 5 Feb 2002, Nicholas Clark wrote: > On Tue, Feb 05, 2002 at 05:19:07PM -0500, Andy Dougherty wrote: > > Well, those and the 86 > > > > cast increases required alignment of target type > > > > warnings we still get all over the place on SPARC :-). > > Gah. You're winning. :-( > The

Re: [PATCH] Nearly the last of the warnings.

Andy Dougherty: > Well, I know (at least) two ways to get rid of the warnings. I just don't > know which one's right. For example, making the bytecode be type > opcode_t* instead of char* gets rid of a lot of them Generally when I see char* in the source, I wonder why it's wrong and what it shou

Re: Parrot Trooper

On Tuesday 05 February 2002 15:46, Melvin Smith wrote: > I'd like to do a Parrot Trooper t-shirt or something along those > lines. Maybe some of you guys have some cool theme we could > use, but I'd like to do it like an award basis so when someone > did something particularly noteworthy or applau

what libc functions are we using?

Some day we're going to want a miniparrot which can build almost anywhere. Just out of curiousity, I was wondering how we're doing as far as being portable. So I wrote this script (attached, along with a makefile patch to invoke it properly). Here are the results: Found 1836 symbols defined

Enternative?

Who understands this? :) op enternative() { goto ADDRESS(( run_native(interpreter, CUR_OPCODE, (opcode_t *)interpreter->c$ } The "goto ADDRESS()" syntax appears to be broken, but I have no idea how to fix it. Here are the compiler messages: gcc: core.ops: In function `Parrot_enternati

Re: Parrot Trooper

On Feb 5, Melvin Smith said: >I'd like to do a Parrot Trooper t-shirt or something along those >lines. Maybe some of you guys have some cool theme we could >use, but I'd like to do it like an award basis so when someone >did something particularly noteworthy or applaudable (spelling?) >for the ca

Re: what libc functions are we using?

At 09:39 PM 2/5/2002 -0500, Josh Wilmes wrote: >Some day we're going to want a miniparrot which can build almost anywhere. >Just out of curiousity, I was wondering how we're doing as far as being >portable. >Of these, 16 are not defined by ANSI C89: > close To comform to ANSI we would probabl

[Patch] A few fixes.

tcc is a rather picky compiler. It found the following: "warnings.c", line 61: Error: [ISO 5.1.1.2]: File does not end in newline character. "misc.c", line 163: Error: [Syntax]: Parse error before '/'. "misc.c", line 541: Error: [ISO 6.1.4]: End of line in string literal. Her