Hi
I assume that BDD(Behavior Driven Development) and the vocabulary that
it implies is not a good choice
at this stage ?
:describe("");
$x.should be(1e5) :it("");
and that a module based on the core testing facilities can be built if
someone feels like to.
Well, the vocabulary that i
Dave Whipp wrote:
I do agree that a prelude.pm should be written atas higher level as
possible, but I would not that Perl6 is not a "declarative" language.
Using the most powerful operators available (I'd like to see more of
them) is about the best you can do: as soon at you start using
codebl
Larry observed:
> My feeling on this is that the compiler should simply hardwire this
> particular adverb so that all the tests can be autogenerated, and the
> multi system never needs to see those versions.
I strongly agree.
> We are merely hijacking the adverb syntax so that is clear which
>
Hi,
I pretty much like this idea. Very perl6ish :)
- I don't think it's important whether it is called :ok, :OK or :test or
:wellhowdidthatworkout. I assume people who will be testing their
modules/code/etc. will be using more advanced modules for testing
anyway. This is for testing the imple
On Tue, Jan 20, 2009 at 1:08 PM, Moritz Lenz wrote:
> So Larry and Patrick developed the idea of creating an
> adverb on the test operator instead:
>
>$x == 1e5 :ok('the :ok makes this is a test');
>
> This is an adverb on the infix:<==> operator, and might
> desugar to something like this:
On Tue, Jan 20, 2009 at 08:08:57PM +0100, Moritz Lenz wrote:
: * We nearly double the number of built-in operators
:by adding an :ok multi
My feeling on this is that the compiler should simply hardwire
this particular adverb so that all the tests can be autogenerated,
and the multi system nev
Perl wrote:
> One of the main fears with this name, "Rakudo Perl 6" - at least when
> it first came out, is that describing Rakudo Perl as, "An
> implementation (one of possibly, many) of the Perl 6 Specification,
> built on top of the Parrot Virtual Machine", will leave people going,
>
>
> > prints 2 instead of giving an intelligent error message that one should
use loop
> > or better yet for 1..3 -> $i { }
> Presumably "say $_" would also yield 2, since I gather the for
is looping over ($i).
$ perl6 -e ' for (my $i = 1; $i <= 3; $i++) { say $i; }'
2
$ perl6 -e ' for (my $i = 1
A few months ago Larry proposed to add some testing
facilites to the language itself, because we want to
culturally encourage testing, and because the test
suite defines the language, so we need to specify the
behaviour of our testing facilities anyway.
We also discussed some possible changes to t
# New Ticket Created by "Eric Hodges"
# Please include the string: [perl #62528]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62528 >
use v6;
rule test {test};
"test" ~~ //;
say '$/.keys => ', $/.keys.perl;
say '%($/).k
# New Ticket Created by mbere...@flashmail.com
# Please include the string: [perl #62540]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62540 >
perl6 -e '$*ERR.say: "hello";' # writes to stderr
This diagnostic type state
# New Ticket Created by "Eric Hodges"
# Please include the string: [perl #62530]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62530 >
class Match is also { method keys () {return %(self).keys }; };
rule a {H};
say "Hello"
On Tue Oct 02 11:01:32 2007, pcoch wrote:
> In src/objects.c:Parrot_ComposeRole() there is the todo item:
>
> * XXX TODO: multi-method handling. */
>
> I think this means that multi-method handling neds to be handled at this
> point in the code.
>
Indeed. Done this in r35820.
Thanks,
Jonathan
Oh,... i see.
Fixed That!
On 19 ene, 15:09, mor...@faui2k3.org (Moritz Lenz) wrote:
> Hi,
>
> dev.null.box wrote:
> > Yes, yes, i know. There is an official perl6 wiki. But, i think a more
> > "friendly" wiki is needed, so i just started a new mediawiki one in
> >http://perl6.wikia.com
>
> I app
Since I can write Perl 6 better than most other languages, and I want to
contribute to Rakudo, and I want some features *now*, and I'm an
impatient bastard... I started an unofficial Perl 6 Prelude project for
Rakudo: http://code.google.com/p/rakudo-prelude/
The intent is to write and collect spec
Is there a rakudo package for cygwin?
There's parrot and parrot-languages, but none of them seems to include
anything that looks like "rakudo" or "perl6".
Do i have to build it myself to try it? Or didn't i look well enough?
Thanks in advance.
--
Amir Elisha Aharoni
heb: http://haharoni.wordp
On Tue, Jan 20, 2009 at 2:20 PM, Jonathan Worthington
wrote:
> chromatic wrote:
>> On Monday 19 January 2009 14:13:22 Bob Rogers wrote:
>>
>>> Do you think that would be fast enough? The usual way for dynamic
>>> languages to get fast compiled numeric code is to bind variables to
>>> hardware typ
chromatic wrote:
On Monday 19 January 2009 14:13:22 Bob Rogers wrote:
Do you think that would be fast enough? The usual way for dynamic
languages to get fast compiled numeric code is to bind variables to
hardware types at compile time, and then inline numeric operations in
order to use that
On Monday 19 January 2009 14:13:22 Bob Rogers wrote:
>On Monday 19 January 2009 13:41:21 Bob Rogers wrote:
>> Math ops:
>> - ceil/floor
>> - transcendental ops
>> - gcd/lcm/fact
>>
>> What are you suggesting as replacements? Or (with
Richard (>):
> Just wanted to say that this afternoon I used rakudo for a real world need.
>
> It was only a simple script to extract data from a text file. But it took
> all of 5 min from start to finish.
>
> Could have done it in perl5, but it really was easier to do it in perl6.
>
> As far as I
On Tuesday 20 January 2009 09:50:56 Patrick R. Michaud wrote:
> > > What's the replacement opcode for n_neg ?
> > If we remove n_neg, the replacement is likely a two-step operation:
> >
> > clone $P1, $P2
> > neg $P1
>
> Please, not this -- it's terribly inconsistent.
>
> When we got rid o
On Tue, Jan 20, 2009 at 09:33:17AM -0800, chromatic wrote:
> On Tuesday 20 January 2009 07:27:53 Patrick R. Michaud wrote:
>
> > On Mon, Jan 19, 2009 at 08:35:26PM -0800, chromatic via RT wrote:
>
> > > I've done most of this in r35787, but we can't get rid of n_neg entirely
> > > until someone u
On Tuesday 20 January 2009 07:27:53 Patrick R. Michaud wrote:
> On Mon, Jan 19, 2009 at 08:35:26PM -0800, chromatic via RT wrote:
> > I've done most of this in r35787, but we can't get rid of n_neg entirely
> > until someone updates PCT and NQP not to use it for prefix:- rules. I
> > poked at th
Hey,
On Tue, Jan 20, 2009 at 11:58 PM, Richard Hainsworth
wrote:
> Just wanted to say that this afternoon I used rakudo for a real world need.
>
> It was only a simple script to extract data from a text file. But it took
> all of 5 min from start to finish.
>
> Could have done it in perl5, but it
Just wanted to say that this afternoon I used rakudo for a real world need.
It was only a simple script to extract data from a text file. But it
took all of 5 min from start to finish.
Could have done it in perl5, but it really was easier to do it in perl6.
As far as I am concerned, this mark
Forgot to mention this is with r31857
- Original Message
From: Parrot via RT
To: is...@yahoo.com
Sent: Monday, January 19, 2009 11:01:42 PM
Subject: [perl #62504] AutoReply: Rakudo segfault on multi type mismatch
Greetings,
This message has been automatically generated in response
On Mon, Jan 19, 2009 at 08:35:26PM -0800, chromatic via RT wrote:
> I've done most of this in r35787, but we can't get rid of n_neg entirely
> until someone updates PCT and NQP not to use it for prefix:- rules. I
> poked at that, but couldn't make them work.
What's the replacement opcode for n_ne
fREW Schmidt wrote:
> I just recently read Ovid's post on use Perl about how we can help by
> fixing PUGS tests. I was a little clear on what he meant and I am a
> little anxious to do something. I checked out the code for parrot
> already and I am getting the pugs code while I write this. Anyon
Author: infinoid
Date: Mon Jan 19 22:51:44 2009
New Revision: 35789
Modified:
trunk/docs/pdds/pdd17_pmc.pod
Changes in other areas also in this revision:
Modified:
trunk/languages/perl6/Test.pm
trunk/src/library.c
Log:
[cage] Fix some codingstd failures.
Modified: trunk/docs/pdds/pdd17
# New Ticket Created by I Sop
# Please include the string: [perl #62506]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62506 >
Following perl6 code segfaults with r31857:
say 8.bla;
# New Ticket Created by I Sop
# Please include the string: [perl #62504]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62504 >
Following perl6 code segfaults:
multi foo($x where { $x == 5 }) { say 'yum' }
foo 8;
Darren Duncan wrote:
1. What we *should* be doing with the Prelude, like with STD.pm, is
write under the assumption that the implementation is also written in
Perl 6.
We should write the Prelude in as declarative a manner as possible,
saying *what* we want to happen rather than how, such as
Hi,
dev.null.box wrote:
> Yes, yes, i know. There is an official perl6 wiki. But, i think a more
> "friendly" wiki is needed, so i just started a new mediawiki one in
> http://perl6.wikia.com
I appreciate your effort, and at the same time I'd like to ask you (and
your fellow contributor(s)) to ac
> Since the tests are all written in Perl 6, you have to learn at least a
> bit of the language.
I figured that; I just wanted to start off with perl6 before I did
anything in PIR.
> In the pugs repo there's a file in t/TASKS that contains a list of
> things to be done - maybe you can start there
34 matches
Mail list logo
