Re: cvs commit: parrot/t/pmc mmd.t

2005-04-06 Thread Leopold Toetsch
Leopold Toetsch <[EMAIL PROTECTED]> wrote: Yesterday on IRC chip and I went a bit through the following problem: > --- integer.pmc 27 Mar 2005 13:14:18 - 1.25 > +++ integer.pmc 5 Apr 2005 16:02:26 - 1.26 > @@ -420,8 +420,23 @@ > >void add (PMC* value, PMC*

Re: [perl #34625] [PATCH] make setup on MSWin32

2005-04-06 Thread Leopold Toetsch
François PERRAD <[EMAIL PROTECTED]> wrote: > I rename too the new script to mk_inno.pl Sorry for bothering you again. But with the recent ICU changes, installing any ICU stuff is obsolete. ICU will be removed from the source tree soon (when we switch to SVN). > Francois Thanks, leo

Re: Perl 6 Summary for 2005-03-22 through 2005-04-05

2005-04-06 Thread Leopold Toetsch
Matt Fowles <[EMAIL PROTECTED]> wrote: >PMC constants > Leo added support for .const things to imc. Unfortunately, the GC eats > them so you can't use it. I forgot to mention that PMC constants are properly marked now. So they are usuable for all PMC types that provide an appropriate

Re: icu

2005-04-06 Thread Leopold Toetsch
Jarkko Hietaniemi wrote: 3) we could probably lift the restriction that we link with c++ I replaced LINK = c++ with LINK = cc in the Makefile and it works. Maybe I'm missing some previous discussion but as long as we are linking ICU in, there is no way that any other linker than the C++ compiler w

Re: Tcl, unicode...

2005-04-06 Thread Leopold Toetsch
William Coleda <[EMAIL PROTECTED]> wrote: > There are 30 unimplmented methods in charset/unicode.h (and a few in > ascii & binary) Yeah. Please folks have a look at it. It's not a big deal. To access one codepoint use ENCODING_GET_CODEPOINT for more in a row use the String_iter. There should be e

Re: [perl #34625] [PATCH] make setup on MSWin32

2005-04-06 Thread Francois PERRAD
At 09:50 06/04/2005 +, you wrote: François PERRAD <[EMAIL PROTECTED]> wrote: > I rename too the new script to mk_inno.pl Sorry for bothering you again. But with the recent ICU changes, installing any ICU stuff is obsolete. ICU will be removed from the source tree soon (when we switch to SVN). O

Re: Regarding status of Parrot and pure perl Perl6 compiler

2005-04-06 Thread Nicholas Clark
On 9 Mar 2005, at 23:34, Millsa Erlas wrote: Also, what is the status of Ponie and providing complete interoperability between Perl 5 language and documented XS support and Parrot and Perl 6? I believe that assuring For various internal and external reasons work has been pretty much stalled for

Re: Regarding status of Parrot and pure perl Perl6 compiler

2005-04-06 Thread Arthur Bergman
On 6 Apr 2005, at 13:50, Nicholas Clark wrote: The roadmap starts with an introduction to Ponie, gives instructions on how to check it out of CVS and build it, and other useful information, so I'll avoid duplicating its contents here. Ponie is using released versions of Perl 5.9.x, rather than

Re: [perl #34625] [PATCH] make setup on MSWin32

2005-04-06 Thread Leopold Toetsch
Francois PERRAD <[EMAIL PROTECTED]> wrote: >> >> > I rename too the new script to mk_inno.pl > OK, without handling ICU, the patch is shorter. Thanks, applied. leo

Re: Regarding status of Parrot and pure perl Perl6 compiler

2005-04-06 Thread Millsa Erlas
Nicholas Clark wrote: On 9 Mar 2005, at 23:34, Millsa Erlas wrote: Also, what is the status of Ponie and providing complete interoperability between Perl 5 language and documented XS support and Parrot and Perl 6? I believe that assuring For various internal and external reasons work has been pr

Re: Regarding status of Parrot and pure perl Perl6 compiler

2005-04-06 Thread Leopold Toetsch
Nicholas Clark <[EMAIL PROTECTED]> wrote: > http://opensource.fotango.com/software/ponie/plan Wow, great detailed plan. Some remarks: 1) objects seem to be missing Parrot is much more object oriented then Perl5. The Perl5 "magic" that depends on custom vtable is basically the task of creating

Monthly Release Schedule

2005-04-06 Thread Chip Salzenberg
I've recently had it suggested that Parrot use a regular release schedule, which tends to maintain momentum and provide many happy opportunities for spreading propaganda^Wnews of our progress. So, wearing my Fearless Leader hat, I announce that from now on we'll be releasing on a regular schedule.

Re: Monthly Release Schedule

2005-04-06 Thread Chip Salzenberg
Nick Clark brings to my attention that I'm missing a footnote: According to Chip Salzenberg: > * What should the standard be for "good enough" in the build? Quite > a few tests will be expected to fail on all platforms. We don't > want a standard that's so rigid it would be at home in

Re: Monthly Release Schedule

2005-04-06 Thread MrJoltCola
At 06:24 PM 4/6/2005, Chip Salzenberg wrote: * What platforms are required for release? I'd guess that we'd get almost of all of our developers (and users, for that matter) with: darwin linux-x86-gcc3.* win32-ms-cl You should round that out with 64-bit Sparc. -Melvin

Re: Monthly Release Schedule

2005-04-06 Thread Chip Salzenberg
According to MrJoltCola: > At 06:24 PM 4/6/2005, Chip Salzenberg wrote: > > * What platforms are required for release? I'd guess that we'd get > >almost of all of our developers (and users, for that matter) with: > > > > darwin > > linux-x86-gcc3.* > > win32-ms-cl > > You shou

Re: Monthly Release Schedule

2005-04-06 Thread Jay Scherrer
T least one FC3 x86_64 Jay Scherrer On Wed, 2005-04-06 at 22:28 -0400, Chip Salzenberg wrote: > According to MrJoltCola: > > At 06:24 PM 4/6/2005, Chip Salzenberg wrote: > > > * What platforms are required for release? I'd guess that we'd get > > >almost of all of our developers (and users, f

Re: Monthly Release Schedule

2005-04-06 Thread MrJoltCola
At 10:28 PM 4/6/2005, Chip Salzenberg wrote: According to MrJoltCola: > At 06:24 PM 4/6/2005, Chip Salzenberg wrote: > > * What platforms are required for release? I'd guess that we'd get > >almost of all of our developers (and users, for that matter) with: > > > > darwin > > linux-