Ciao Mattia,
thanks for your reply. I read a bit about ABI and I guess it's
something I only want to touch with a long pole, that pole being an
extra layer of indirection I initially hoped to be able to avoid.
I like the idea of leveraging the wxPerl XS files. Any comments on why
you introduced
eval("print 1", :lang)
require_parrot 'foo.pir';
Would it also be possible to somehow 'link' it with a parrot bytecode
file?
Regards,
Christian
--
[EMAIL PROTECTED] - http://christian.web42.com - http://www.web42.com/crenz/
"The computer should be doing the hard work. That's what it
Hi!
> I like the idea of leveraging the wxPerl XS files. Any comments on why
> you introduced xsubppp (on top of xsubpp) for some XS files?
XS++ is much less verbose than plain XS when writing
C++ code [1], and it allows me to handle some C++ features
(like passing/returning references) without
On Sat, 22 Oct 2005 [EMAIL PROTECTED] wrote:
If we find a lot of yen signs as zip-operators in the standard
library, Japanese would have a big question: "Give up either
Perl6 or Windows. Which do we need?" And I suppose the answer
Hmmm, begins to sound interesting... ;-P
Michele
--
voices
> The current list of fears is:
You don't include my personal fear.
FEAR: I will need a lobotomy before I can make sense of Perl 6!
--
Stop the infinite loop, I want to get off! http://surreal.istic.org/
Paraphernalia/Never hides your broken bones,/ And I don't know why you'd
want to try:/ I
Here is my part.
On Oct 24, 2005, at 07:20 , Juerd wrote:
I've created pugs/docs/quickref/fears, a list of Perl 6 fears.
Feel free to add your own, or fears you heard about!
[snip]
: FEAR: Perl 6 has too many operators!
FEAR: Perl 6 has so many operators that it runs out of Unicode
characte
Hi,
S04 says thus:
The default case:
default {...}
is exactly equivalent to
when true {...}
However, that parses to:
if $_ ~~ bool::true { ...; leave }
Which is not executed if $_ is false, unless ~~ bool::true does
something special. Perhaps default should be eq
Daniel Hulme skribis 2005-10-24 9:00 (+0100):
> FEAR: I will need a lobotomy before I can make sense of Perl 6!
This falls under "hard to learn".
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_juerd_n.html
Feel free to add your own, or fears you heard about!
Fear: Perl 6 will not attract enough interested developers and
companies to gain momentum. People will continue to be excited about
digital watches and PHP 5.
Regards,
Christian
--
[EMAIL PROTECTED] - http://christian.web42.com - http://w
I'm mentally going over the ways to do it.
class Foo;
# the perl5 way
use base <>;
sub new {
my $class = shift;
my $self = $class.SUPER::new(@_); # syntax?
return $self;
}
sub do_it {
my($self, $arg) = @_;
say "doing $arg!";
}
class Foo is Base {
# the perl6 way
m
Christian Renz wrote:
Feel free to add your own, or fears you heard about!
Fear: Perl 6 will not attract enough interested developers and
companies to gain momentum. People will continue to be excited about
digital watches and PHP 5.
I think Perl 6 will take time to insterest developers. One
Christian Renz skribis 2005-10-24 15:31 (+0200):
> >Feel free to add your own, or fears you heard about!
> Fear: Perl 6 will not attract enough interested developers and
> companies to gain momentum. People will continue to be excited about
> digital watches and PHP 5.
That's already expressed in:
Leopold Toetsch wrote:
> >> + #$P1 is now a array-like container PMC with three Integer elements.
> The question is of course, which type of PMC array?
The answer is surely, the array-type of the current HLL (as returned by
Parrot_get_ctx_HLL_type).
> does JSON define to deal with self-referenti
On Oct 23, 2005, at 6:44 PM, Leopold Toetsch wrote:
On Oct 21, 2005, at 18:07, Will Coleda wrote:
There is now rudimentary support for converting parrot objects to
JSON strings.
+ # generate a JSON representation of a PMC.
+ $S0 = _json( $P0 )
$P0 = new .Array
$P0[0] = $P0
et
On 10/24/05, Juerd <[EMAIL PROTECTED]> wrote:
>
> > >Feel free to add your own, or fears you heard about!
FEAR: Perl6 internals will be just as inaccessable as p5
FEAR: The Perl6 process is driving away too many good developers
FEAR: Perl6 will not be as portable as p5
FEAR: Perl6 will not be
On 10/24/05, Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
>
> On 10/24/05, Juerd <[EMAIL PROTECTED]> wrote:
> >
> > > >Feel free to add your own, or fears you heard about!
>
>
This really isn't a fear as much as it is a complaint. It has to do with
design decisions and the list.
"Perl 5 was my rewrit
On Mon, Oct 24, 2005 at 02:47:58PM +0100, Alberto Manuel Brandão Simões wrote:
> Another is because it will take too long to port all CPAN modules to
> Perl 6 (for this I suggest a Porters force-task to interact with current
> CPAN module owners and help and/or port their modules).
I think Autri
I fear that, at age 70, I shall not live long enough to become efficient with
perl 6.
Two full years ago I purchased and read "Perl 6 Essentials". That lead me to
this list which I have enjoyed but never felt competent to contribute much.
Pretty much all of what I leaned in Essentials has been
HaloO,
Luke Palmer wrote:
On 10/20/05, Larry Wall <[EMAIL PROTECTED]> wrote:
Another thing I didn't mention is that that binds both the variable
and its class. But the $ variable is of course optional after the
type, so you could just write that
sub sametype (¢T, ¢T) {...}
if you don't a
On 10/24/05, John Macdonald <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 24, 2005 at 02:47:58PM +0100, Alberto Manuel Brandão Simões wrote:
> > Another is because it will take too long to port all CPAN modules to
> > Perl 6 (for this I suggest a Porters force-task to interact with current
> > CPAN modu
Joshua Gatcomb wrote:
On 10/24/05, Juerd <[EMAIL PROTECTED]> wrote:
Feel free to add your own, or fears you heard about!
FEAR: The Perl6 process is driving away too many good developers
FEAR: Perl6 will not be as portable as p5
FEAR: Perl6 is un-necessary and the time, money, and resources
On 10/24/05, Nate Wiger <[EMAIL PROTECTED]> wrote:
> Joshua Gatcomb wrote:
> > On 10/24/05, Juerd <[EMAIL PROTECTED]> wrote:
> >
> Feel free to add your own, or fears you heard about!
> >
> > FEAR: The Perl6 process is driving away too many good developers
> >
> > FEAR: Perl6 will not be as por
Nate Wiger skribis 2005-10-24 10:44 (-0700):
> The fact that there's not alot of active p5p'ers on this list should
> alarm people more.
I don't know about the other Perl 6 lists, are they as p5porterless?
It does not alarm me that they are not *here*, this being a list where
we mostly discuss t
On Wed, Oct 19, 2005 at 09:59:15PM +0100, Nicholas Clark wrote:
> I think the better solution is going to be to keep them in src/extend.c,
> and auto-generate a second file for the vtable calls. So the version attached
> generates src/extend_vtable.c
I like that separation.
> chromatic:
> > I thi
A question recently arose (about extend.c) about when it's OK to
change a public API, or remove it as obsolete.
Mostly I want to avoid surprise breakages. Not that I can eliminate
them. (I suspect I'll be responsible for a good number of them. New
lexical subsystem, anyone?) But for smaller th
I'll attempt to answer a couple of the Parrot fears. :-)
"Doug McNutt" <[EMAIL PROTECTED]> wrote:
I fear that Parrot will not come into widespread use until perl 6 is
released.
Parrot might not be ready to come into widespread use until Perl 6 is
released - there's some stuff missing yet. B
Hi Nick,
I've added a src test that shows iteration through a hash from C
(t/src/hash.t #10) and disabled capturing SIGHUP, as mentioned on
#parrotsketch.
The other TODO [1] will take a bit of time. Currently the hash buckets
are filled from right to left, which makes iteration not stable, w
> [leo - So 23. Okt 2005, 12:25:29]:
> > As Parrot_setup_args() is so far only used for passing 'output' to the
> > exec runcore, I propose a quick fix.
> >
> > i. Do not use STRING register for passing options
> > ii. Move interp->imc_info->output to interp->output_file and use
> > interp->outpu
On 10/23/05, Ilmari Vacklin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> S04 says thus:
>
> The default case:
>
> default {...}
>
> is exactly equivalent to
>
> when true {...}
>
> However, that parses to:
>
> if $_ ~~ bool::true { ...; leave }
>
> Which is not executed if $_ is
The subroutine check_progs defined in lib/Parrot/Configure/Step.pm is not
portable (doesn't work on MSWin32).
On MSWin32, the real filename of a program is prog.exe, prog.com, prog.bat
or prog.cmd , so if -x 'prog' is not enough.
This subroutine is currently used by config/inter/lex.pl & yacc
On 10/24/05, TSa <[EMAIL PROTECTED]> wrote:
> Does this capturing of the type into ¢T also involve runtime
> code template expansion? That is, if sametype(Int,Int) didn't
> exist it would be compiled on the fly for a call sametype(3,2)?
I think that's up to the implementation. From the language
p
31 matches
Mail list logo
