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*
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
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
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
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
Is there a way tests to determine that a module cannot be installed on a
platform so that CPANPLUS or CPAN::YACSmoke can issue an "NA" (Not
Applicable) report?
CPANPLUS relies on module names (e.g. "Solaris::" or "Win32::") but that
is not always appropriate in cases where a module runs on many
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).
Aaron Sherman <[EMAIL PROTECTED]> writes:
> http://www.cs.tut.fi/~jkorpela/emacs-iso.html
Coincidentally, last week the emacs developers decided to declare
iso-accents mode (dated 1998) obsolete. Emacs 21 (out for several
years now) has native support for language encodings.
-- Johan
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
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
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
Larry Wall wrote:
Yes. It should complain that = is not a valid type signature.
Any &foo (or &foo:<...>) followed by <...> should be parsed as a single
term selecting the function that MMD would dispatch to given that
type signature.
And I guess it's not allowed to have interspersed whitespace unl
On 5 Apr, Lev Selector wrote:
: These things don't work in pugs yet, right?
:
: =
: arrays of arrays
: hash of hashes
: etc.
:
: @ar.elems
: @ar.last
I'm not sure about AoA's, HoH's, etc. since I don't have a working
pugs installation (yet), due to ghc n
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
Thomas Sandlaà writes:
> Larry Wall wrote:
> >Yes. It should complain that = is not a valid type signature.
> >Any &foo (or &foo:<...>) followed by <...> should be parsed as a single
> >term selecting the function that MMD would dispatch to given that
> >type signature.
>
> And I guess it's not a
On Wed, Apr 06, 2005 at 04:31:08PM +0200, Thomas Sandlaß wrote:
: Larry Wall wrote:
: >Yes. It should complain that = is not a valid type signature.
: >Any &foo (or &foo:<...>) followed by <...> should be parsed as a single
: >term selecting the function that MMD would dispatch to given that
: >ty
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
On Wed, Apr 06, 2005 at 10:07:33AM -0600, Luke Palmer wrote:
: Thomas Sandlaß writes:
: > Larry Wall wrote:
: > >Yes. It should complain that = is not a valid type signature.
: > >Any &foo (or &foo:<...>) followed by <...> should be parsed as a single
: > >term selecting the function that MMD woul
HaloO Larry,
you wrote:
for ordinary functions. If it gets really popular people might
even start writing:
sub foo :(Str,Int) {...}
I like it, but that could mean it will not become popular :))
And this is also nice:
sub foo :(Str,Int) of Str {...}
Is a closure return type indicated with this
On Mon, Apr 04, 2005 at 06:50:11PM +0200, Thomas Sandlaß wrote:
: Juerd wrote:
: >And will Perl 6 reference values rather than their containers, that is:
: >will \$foo differ when $foo gets a new value, just as in Python id(foo)
: >changes after foo += 1?
:
: Depends on the definition of the seman
Larry Wall skribis 2005-04-06 11:10 (-0700):
> $$ref follow the ref list to the actual object.
my $foo;
my $bar = \$foo;
my $quux = \$bar;
my $xyzzy = \$quux;
How then, with only $xyzzy, do you get $bar? $$xyzzy would follow until
$foo. I don't like this at all.
> $ref.fo
On Wed, Apr 06, 2005 at 07:22:48PM +0200, Thomas Sandlaß wrote:
: HaloO Larry,
:
: you wrote:
: >for ordinary functions. If it gets really popular people might
: >even start writing:
: >
: >sub foo :(Str,Int) {...}
:
: I like it, but that could mean it will not become popular :))
: And this
On Wed, Apr 06, 2005 at 08:24:23PM +0200, Juerd wrote:
: Larry Wall skribis 2005-04-06 11:10 (-0700):
: > $$ref follow the ref list to the actual object.
:
: my $foo;
: my $bar = \$foo;
: my $quux = \$bar;
: my $xyzzy = \$quux;
:
: How then, with only $xyzzy, do you get $bar
On Wed, Apr 06, 2005 at 11:30:35AM -0700, Larry Wall wrote:
> If you want to help, earn a billion dollars and write me into your
> will. And then peg out. Nothing personal. :-)
>
> Larry
Darn. So far, I'm, 0 for 3 on that plan.
However, I promise that item two will follow very shortly in
tim
Larry Wall wrote:
On Wed, Apr 06, 2005 at 08:24:23PM +0200, Juerd wrote:
: Larry Wall skribis 2005-04-06 11:10 (-0700):
: > $$ref follow the ref list to the actual object.
:
: my $foo;
: my $bar = \$foo;
: my $quux = \$bar;
: my $xyzzy = \$quux;
:
: How then, with only $xyzzy,
On Wed, Apr 06, 2005, Larry Wall wrote:
> I think it's time to break out
> the colon again and use something like:
>
> &infix:<+>:(Complex, Complex);
>
> or
>
> &foo:(Str,Int)
>
> for ordinary functions. If it gets really popular people might
> even start writing:
>
> sub foo :(S
Larry Wall skribis 2005-04-06 11:37 (-0700):
> : my $foo;
> : my $bar = \$foo;
> : my $quux = \$bar;
> : my $xyzzy = \$quux;
> : How then, with only $xyzzy, do you get $bar? $$xyzzy would follow until
> : $foo. I don't like this at all.
> You can't get at $bar anyway. You can only
On Wed, 2005-04-06 at 14:37, Larry Wall wrote:
> On Wed, Apr 06, 2005 at 08:24:23PM +0200, Juerd wrote:
> : Larry Wall skribis 2005-04-06 11:10 (-0700):
> : > $$ref follow the ref list to the actual object.
> :
> : my $foo;
> : my $bar = \$foo;
> : my $quux = \$bar;
> : my $xyz
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.
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
Steven,
I do have recent installation:
pugs -> /usr/local/ActivePerl-5.8/bin/pugs (Version: 6.0.13)
ghc -> ghc-6.4
But I can't make Arrays of Arrays or Hash of Hashes work.
@ar.elems & @ar.last don't work either.
Unless I am doing something wrong - then may be somebody
can show an example of usage
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
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
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
On Wed, Apr 06, 2005 at 02:43:55PM -0500, Patrick R. Michaud wrote:
: On Wed, Apr 06, 2005, Larry Wall wrote:
: > I think it's time to break out
: > the colon again and use something like:
: >
: > &infix:<+>:(Complex, Complex);
: >
: > or
: >
: > &foo:(Str,Int)
: >
: > for ordinary fun
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-
36 matches
Mail list logo
