[Patch] const fix for gcc warnings

2002-02-17 Thread Josh Wilmes
[josh-003.patch] This patch adds some missing const's to silence a number of gcc warnings. --Josh Index: include/parrot/warnings.h === RCS file: /home/perlcvs/parrot/include/parrot/warnings.h,v retrieving revision 1.1 diff -u -r1

[Corrected Patch] Rollup of my current-outstanding patches

2002-02-17 Thread Josh Wilmes
Sorry, I goofed on that last patch- corrected version (including rx.h this time): [josh-002.patch] This patch rolls up all my current outstanding patches. - add makefile target and script to test for external libc dependencies - fix return values in hash and array PMCs (returning 0 in a

Re: [PATCH] make core_ops_prederef.c compile with MS c++

2002-02-17 Thread Josh Wilmes
Daniel, I've actually got something equivalent for the inline portion of your patch in the patch I just sent to the list. As far as the ssize_t part, yeah, this probably belongs in config.h_in or parrot.h or something. --Josh At 0:30 on 02/18/2002 +0100, "Ritz Daniel" <[EMAIL PROTECTED]> wr

Re: PDDs, guys.

2002-02-17 Thread Josh Wilmes
Bravo! PDD 7 (coding standards) is also still MIA, although i understand that it's basically complete. --Josh At 16:18 on 02/17/2002 GMT, Simon Cozens <[EMAIL PROTECTED]> wrote: > I was just starting to think about writing something on the history and > evolution of Parrot's design, and came

[Patch] Rollup of my current-outstanding patches

2002-02-17 Thread Josh Wilmes
This patch rolls up all my current patches which haven't yet been applied: - add makefile target and script to test for external libc dependencies - fix return values in hash and array PMCs (returning 0 in a void func) - remove unnecessary data pointer <=> function pointer conversions

Re: PDDs, guys.

2002-02-17 Thread Buggs
On Sunday 17 February 2002 17:18, Simon Cozens wrote: > Yes, I'm being an anal retentive asshole. It's my job. Nah, this time you are not ;P On to the pdds ... There seems to be some part missing from pdd2, at the bottom. And this takes care of the dublicate entries in pdd6, as they seem to ha

[PATCH] make core_ops_prederef.c compile with MS c++

2002-02-17 Thread Ritz Daniel
this is a quick fix for CPrederef.pm to make to generated code compile with the MS compiler. fixes: - ms compiler allows inline only for c++, for c there's __inline - ms header files knows nothing about ssize_t may be this should go into parrot.h?? Index: CPrederef.pm ===

Re: [PDD] Regular Expressions

2002-02-17 Thread Simon Cozens
Brent Dax: > This is the first draft of my proposed regex PDD. Review and advise. You rock, sir. Analysis in the morning. -- FAILURE: When Your Best Just Isn't Good Enough http://www.despair.com

RE: [Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Melvin Smith
>-Melvin >-Melvin Sorry, I got stuck in a for loop. :)

Re: [Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Steve Fink
On Sun, Feb 17, 2002 at 08:54:52PM +0100, Gerson Kurz wrote: > Besides, wasn't parrot supposed to be a VM and interpret the code, > rather than just compile-to-c? (And, the code doesn't even look like > normal C code - it has a "static char program_code[] = {" which it > executes). Yes. You're us

RE: [Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Melvin Smith
At 09:38 PM 2/17/2002 +0100, Gerson Kurz wrote: >~/parrot>assemble.pl examples/assembly/euclid.pasm >test.pbc >~/parrot>pbc2c.pl test.pbc >test.c >Use of uninitialized value in sprintf at lib/Parrot/OpTrans/CGoto.pm line >97. >~/parrot> Just run the bytecode with the interpreter instead. ../test

RE: [Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Jonathan Stowe
On Sun, 17 Feb 2002, Gerson Kurz wrote: > Hi Brent, > > you wrote: > > Did you follow the directions in the README file? That assemble.pl > > warning especially makes me very suspicious. > > I'm sorry, I got it wrong in the mail. I did the configure/make/make test > thing. This is what happened:

RE: [Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Gerson Kurz
Hi Brent, you wrote: > Did you follow the directions in the README file? That assemble.pl > warning especially makes me very suspicious. I'm sorry, I got it wrong in the mail. I did the configure/make/make test thing. This is what happened: ~/parrot>assemble.pl examples/assembly/euclid.pasm >t

RE: [Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Brent Dax
Gerson Kurz: # I downloaded # # http://cvs.perl.org/snapshots/parrot/parrot_2002-02-17_14.tar.gz # # to try fooling around with parrot on cygwin. # # 1) Some files are missing, so make.pl fails. Luckily for me I'm not an # alpha-or-sun-user (missing: jit/sun4/lib.jit and string.jit - they are

[PDD] Regular Expressions

2002-02-17 Thread Brent Dax
This is the first draft of my proposed regex PDD. Review and advise. --Brent Dax [EMAIL PROTECTED] Parrot Configure pumpking, regex hacker, embedding coder, and all-around good guy Check out the Parrot FAQ: http://www.panix.com/~ziggy/parrot.html (no, it's not mine) . hawt sysadmin chx0rs

[Parrot-Newbie] Fooling around with parrot

2002-02-17 Thread Gerson Kurz
I downloaded http://cvs.perl.org/snapshots/parrot/parrot_2002-02-17_14.tar.gz to try fooling around with parrot on cygwin. 1) Some files are missing, so make.pl fails. Luckily for me I'm not an alpha-or-sun-user (missing: jit/sun4/lib.jit and string.jit - they are there in the archive but 0

RE: [PATCH] Parrot_Interp

2002-02-17 Thread Brent Dax
Simon Cozens: # Brent Dax: # > I was afraid you were gonna say that. :^) I'll put it # back in my next # > embedding patch. # # And document this exchange in the Embedding PDD? :) I probably will--after I write the regex PDD. :^) --Brent Dax [EMAIL PROTECTED] Parrot Configure pumpking, regex

Re: [PATCH] Parrot_Interp

2002-02-17 Thread Simon Cozens
Brent Dax: > I was afraid you were gonna say that. :^) I'll put it back in my next > embedding patch. And document this exchange in the Embedding PDD? :) -- Ever wake up feeling like a null pointer? -Allan Pratt

RE: [PATCH] Parrot_Interp

2002-02-17 Thread Brent Dax
Dan Sugalski: # On Sun, 17 Feb 2002, Brent Dax wrote: # # > Melvin Smith: # > # At 06:59 PM 2/16/2002 -0800, Steve Fink wrote: # > # >Anyone object to eliminating the need for the 'struct'? # > # >-struct Parrot_Interp { # > # >+typedef struct Parrot_Interp { # > # > struct IReg int_reg; # >

Keys and Indices PDD

2002-02-17 Thread Simon Cozens
(Ziggy, could you give this a number and commit it to CVS when you have time? Thanks. I'll update the CVS copy with comments from this thread when it is done.) Here's a first approximation at half a PDD, but it should be enough to chew over. Please note particularly the sections. Thanks. =head1

RE: [PATCH] Parrot_Interp

2002-02-17 Thread Dan Sugalski
On Sun, 17 Feb 2002, Brent Dax wrote: > Melvin Smith: > # At 06:59 PM 2/16/2002 -0800, Steve Fink wrote: > # >Anyone object to eliminating the need for the 'struct'? > # >-struct Parrot_Interp { > # >+typedef struct Parrot_Interp { > # > struct IReg int_reg; > # > struct NReg num_reg; >

RE: [PATCH] Parrot_Interp

2002-02-17 Thread Brent Dax
Melvin Smith: # At 06:59 PM 2/16/2002 -0800, Steve Fink wrote: # >Anyone object to eliminating the need for the 'struct'? # >-struct Parrot_Interp { # >+typedef struct Parrot_Interp { # > struct IReg int_reg; # > struct NReg num_reg; # > struct SReg string_reg; # >@@ -87,7 +86,7 @@

Re: [PATCH] Parrot_Interp

2002-02-17 Thread Melvin Smith
At 06:59 PM 2/16/2002 -0800, Steve Fink wrote: >Anyone object to eliminating the need for the 'struct'? >-struct Parrot_Interp { >+typedef struct Parrot_Interp { > struct IReg int_reg; > struct NReg num_reg; > struct SReg string_reg; >@@ -87,7 +86,7 @@ > void *current_package;

PDDs, guys.

2002-02-17 Thread Simon Cozens
I was just starting to think about writing something on the history and evolution of Parrot's design, and came across some PDDs in the mail archives. Grief, I remember these things! These were meant to document the design, what we'd decided, why those decisions were a bad idea, what we chose inste

Re: [PATCH] Bash some more warnings

2002-02-17 Thread Segher Boessenkool
Steve Fink wrote: > > > - key->keys = (KEY_PAIR*)realloc(key->keys,sizeof(KEY_PAIR)*size); > > + key->keys = (KEY_PAIR**)realloc(key->keys,sizeof(KEY_PAIR)*size); > > That seems rather suspicious. I don't know anything about the KEY_PAIR > type, but allocating a chunk of memory big e

Anyone understand the assembler?

2002-02-17 Thread Simon Cozens
*sigh*. Gone are the days when this was a simple 500 line Perl script. I'm trying to add two new output types, and I've got half way through before tying myself in knots. If anyone can look at my diff and finish the missing bits, please drop me a mail. -- In this talk, I would like to speculate

[REPATCH] Re: [PATCH] Bash some more warnings

2002-02-17 Thread Jonathan Stowe
On Sat, 16 Feb 2002, Steve Fink wrote: > > - key->keys = (KEY_PAIR*)realloc(key->keys,sizeof(KEY_PAIR)*size); > > + key->keys = (KEY_PAIR**)realloc(key->keys,sizeof(KEY_PAIR)*size); > > That seems rather suspicious. I don't know anything about the KEY_PAIR > type, but allocating a chunk