On Fri, Aug 05, 2005 at 11:46:19AM -0500, [EMAIL PROTECTED] wrote:
> While trying to use say for debugging, I ran across an oddity. While I can:
> say "[EMAIL PROTECTED]";
> and
> say @some_array;
> this doesn't work:
> say "@some_array";
If you're expecting to see the contents of @some_array,
> So the question is: is that file installed properly to your --prefix
> directory structure?
> Maybe you are querying the wrong parrot too (the config paths and
> settings gets compiled into the executable of parrot)?
It is installed properly and I am not querying but the pugs config is doing
it
I am creating my first module (finally) and I was told a while ago to use
Module::Starter. Which I did. I am fine there. When I look at the code
generated I see that all the POD stuff is inline while I prefer to see POD
stuff at the end. Is the inline POD the current preferred way? If it is, I
am f
Michael G Schwern wrote:
On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger wrote:
There are some tests that I would love to have abort as soon as they
fail. (If step 3 failed, then steps 4 and 5 are places I don't want to
go) Is there a way to make prove do this? I skimmed the
Test::Build
On Sat, Aug 06, 2005 at 01:51:17AM +0400, Andrew Shitov wrote:
> > Parrot 0.2.3 "Serenity" Released!
>
> Possibly I'm growling again but I cannot run any Perl 6 programme with
> new Parrots.
>
> One-liner test.p6 containing 'print "perl 6";' is compiled to test.imc and
> cause an error:
The REA
On Thu, Aug 04, 2005 at 09:29:21PM +0400, Andrew Shitov wrote:
: in fact, that is exactly
:
: (print.getArgument(3) * 3); the same as above.
:
: so why not 'print($x)' == 'print ($x)' ;-)
Because most people's expectations diverge from yours, actually, and
we got tired of answering the FAQ.
> Parrot 0.2.3 "Serenity" Released!
Possibly I'm growling again but I cannot run any Perl 6 programme with
new Parrots.
One-liner test.p6 containing 'print "perl 6";' is compiled to test.imc and
cause an error:
C:\parrot-0.2.3\languages\perl6>perl perl6 test.p6
error:imcc:syntax error, unexpect
On Aug 5, 2005, at 20:17, Sam Ruby wrote:
My experiences with Parrot was that everything I did was
met with either direct animosity or by being ignored. If that changed,
I could see myself becoming active again.
I would very much appreciate your contributions the more that parrot
was and
Seems like you left out the degenerate case for when you run out of pairs:
sub infix: (Scalar $x, 0) { $x }
On 2005-08-05 16:24, "Yuval Kogman" <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 05, 2005 at 11:36:16 -0700, Larry Wall wrote:
>
>> There's something to be said for having a way of inde
On Fri, Aug 05, 2005 at 11:36:16 -0700, Larry Wall wrote:
> There's something to be said for having a way of indexing into that
> using numeric subscripts. Certainly Lisp's extensible car/cdr notation
> is the wrong way to do it, but cdddr is certainly shorter than
>
> $pair.value.value.valu
On Fri, Aug 05, 2005 at 12:27:53AM +0200, Ingo Blechschmidt wrote:
: Hi,
:
: Andrew Shitov wrote:
: >> say $pair[0]; # a?
: >
: > It looks like $pair is an arrayref while 'say ref $pair' tells 'Pair'.
:
: right, this is why I asked, IMHO it's bogus.
Yes, for bare pairs, it's probably somew
Leopold Toetsch wrote:
> Citing 33.html:
>
> "Parrot's current implementation relies on the ability to "morph" an
> object to another type. Leo has attempted to challenge this a number of
> times, but to my knowledge never successfully."
>
> I'm a bit bewildered that pirate folks seem not to bot
On 8/5/05, Ingo Blechschmidt <[EMAIL PROTECTED]> wrote:
> Hi,
>
> ~Str;# ""? "Str"?
"Str"
> ~::Str; # ""? "Str"?
I don't know how :: works anymore. I'll avoid these.
> ~Str.meta; # ""? (fill in please)?
"Class"
>
On 8/5/05, Ingo Blechschmidt <[EMAIL PROTECTED]> wrote:
> Hi,
>
> my $str = "Hello";
> $str.ref = Int; # allowed?
> $str.meta = &some_sub.meta; # allowed?
I hardly think those work. Both of those require a change of
implementation, which we can't do generically. So
Hi,
[EMAIL PROTECTED] wrote:
> While trying to use say for debugging, I ran across an oddity. While
> I can:
> say "[EMAIL PROTECTED]";
> and
> say @some_array;
> this doesn't work:
> say "@some_array";
Pugs is correct here, you need to use [] or {} to interpolate
aggregates:
say "$sc
While trying to use say for debugging, I ran across an oddity. While I can:
say "[EMAIL PROTECTED]";
and
say @some_array;
this doesn't work:
say "@some_array";
Even stranger:
class SomeClass {
has $.scalar_attr;
has @.array_attr;
method trial () {
say "$.scalar_attr @.array_att
"François PERRAD (via RT)" <[EMAIL PROTECTED]> wrote:
With this patch, dynclasses work with MinGW32.
(same as r8717 by Jonathan Worthington with MSC)
Unfortunately, your changes to dynclasses_pl.in break the build for MSVC.
Fortunately, it looks to be something fairly minor.
-"${ld
On Thu, Aug 04, 2005 at 10:48:49PM -0700, Brent 'Dax' Royal-Gordon wrote:
: Luke Palmer <[EMAIL PROTECTED]> wrote:
: > On 8/4/05, Ingo Blechschmidt <[EMAIL PROTECTED]> wrote:
: > > my $undef = undef;
: > > say $undef.chars? # 0? undef? die?
: > > say chars $undef; # 0? undef? die?
:
Parrot 0.2.3 "Serenity" Released!
On behalf of the Parrot team I'm proud to announce another monthly
release of Parrot and I'd like to thank all involved people as well as
our sponsors for supporting us.
What is Parrot?
Parrot is a virtual machine aimed at running Perl6 and other dynamic
langua
Hi,
my $str = "Hello";
$str.ref = Int; # allowed?
$str.meta = &some_sub.meta; # allowed?
my $str = "Hello";
Str ::= Int; # allowed?
::Str ::= ::Int;# or is this allowed?
say $str; # still "Hello"?
Hi,
~Str;# ""? "Str"?
~::Str; # ""? "Str"?
~Str.meta; # ""? (fill in please)?
~::Str.meta; # ""? (fill in please)?
+Str; +::Str;
+Str.meta; +::Str.meta; # all errors?
?Str;
Please no more checkins to parrot svn until further notice.
Thanks,
leo
On Thu, 2005-08-04 at 08:52 -0400, Amir Karger wrote:
> I'm about to commit an updated version of leo's Z-code-to-PIR
> translator. I'm wondering what I should do about t.
I hope to have a variant of Test::More written in pure PIR in the near
future (though it probably requires the new calling co
23 matches
Mail list logo
