Randy W. Sims wrote:
Conrad Schneiker wrote:
From: Randy W. Sims [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 1:12 AM
[...]
What about getting it added at gmane.org also?
Seems like a great idea. (Just learned about it, thanks to your post.)
Would you be willing to follow up?
I
Woah, we are getting really far away from talking about perl6 here...
- ask
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> On Sat, Jun 03, 2006 at 03:51:45PM -0700, Paul Hodges wrote:
> : { no threads;
> :print @_.»();
> : }
>
> It seems a bit odd to use a construct for its syntactic sugar value
> but take away its semantics...
>
> If you just need ordering, this (o
Thanks!...Scott
--- James E Keenan <[EMAIL PROTECTED]> wrote:
> Scott Wang wrote:
> > Hi James,
> >
> > Any information on, generally, how and why
> > Devel::Cover use B::Deparse module?
>
> Google is your friend. I recommend going to Google
> Groups and searching
> the archives for perl.qa
Author: larry
Date: Sat Jun 3 20:43:33 2006
New Revision: 9466
Modified:
doc/trunk/design/syn/S03.pod
Log:
typo from scook0++
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod(origin
Author: larry
Date: Sat Jun 3 20:32:43 2006
New Revision: 9465
Modified:
doc/trunk/design/syn/S03.pod
Log:
Revisions to definitions of simple scalar.
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/sy
Scott Wang wrote:
Hi James,
Any information on, generally, how and why
Devel::Cover use B::Deparse module?
Google is your friend. I recommend going to Google Groups and searching
the archives for perl.qa for B::Deparse.
I saw tons of
messages "Deep recursion on subroutine
"B::Deparse::fi
Hi All.
Has anyone successfully used Devel::Cover under mod_perl to do
coverage for a mason application?
My preliminary experiments were mixed. I used D::C from my .pl
handler file and ran apache with -X, but saw inconsistent results
when i did a couple tests.
During the first test, it
On 6/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
+$a # simple scalar variable
+@a[123]# single literal subscript
+%a{'x'}# single literal subscript
+%a # single literal subscript
+@a[+TERM] # single term coerced to numeric for array
+%a{~TERM}
Author: larry
Date: Sat Jun 3 19:45:11 2006
New Revision: 9463
Modified:
doc/trunk/design/syn/S03.pod
Log:
Change default lvalue parsing to default to list, with short list of scalars.
Modified: doc/trunk/design/syn/S03.pod
===
Author: larry
Date: Sat Jun 3 19:13:10 2006
New Revision: 9462
Modified:
doc/trunk/design/syn/S12.pod
Log:
Clarified scoping of "has $x" and friends.
Modified: doc/trunk/design/syn/S12.pod
==
--- doc/trunk/design/sy
Hi James,
Any information on, generally, how and why
Devel::Cover use B::Deparse module? I saw tons of
messages "Deep recursion on subroutine
"B::Deparse::find_scope"" in our test logs. The
information on how and why might help us figure out
the reason that these messages show up in our logs.
Tha
On Sat, Jun 03, 2006 at 03:51:45PM -0700, Paul Hodges wrote:
: --- Ashley Winters <[EMAIL PROTECTED]> wrote:
: > On 6/2/06, Paul Hodges <[EMAIL PROTECTED]> wrote:
: > >
: > > my @answer = map { async { &_() } } @jobs;
: >
: > That still seems too explicit. I thought we had hyperoperators to
: > i
A. Pagaltzis schrieb:
> * Thomas Wittek <[EMAIL PROTECTED]> [2006-06-03 22:30]:
>> Interestingly it is very similar to Markdown although I never
>> heard about it before :)
>
> Hmm, it doesn’t look similar at all to me?
Headers (Markdown):
# This is an H1
## This is an H2
## This is an H6
He
--- Ashley Winters <[EMAIL PROTECTED]> wrote:
> On 6/2/06, Paul Hodges <[EMAIL PROTECTED]> wrote:
> >
> > my @answer = map { async { &_() } } @jobs;
>
> That still seems too explicit. I thought we had hyperoperators to
> implictly parallelize for us:
>
> my @answer = @jobs.»();
>
> Which would
(For the p6c readers who don't also read p6i, I'm the person who is
implementing software transactional memory in Parrot as a Summer of
Code project.)
Attached is a tentative design for the PASM-visible interface to
software transactional memory. The document is also available at
https://svn.perl
* Thomas Wittek <[EMAIL PROTECTED]> [2006-06-03 22:30]:
> Interestingly it is very similar to Markdown although I never
> heard about it before :)
Hmm, it doesn’t look similar at all to me? Not even superficially
similar, but most importantly, it looks line-based. Markdown is
block-based. If you w
Conrad Schneiker wrote:
From: Randy W. Sims [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 1:12 AM
[...]
What about getting it added at gmane.org also?
Seems like a great idea. (Just learned about it, thanks to your post.)
Would you be willing to follow up?
I submitted the request
A. Pagaltzis schrieb:
> * Amir E. Aharoni <[EMAIL PROTECTED]> [2006-05-28 23:00]:
>> The popularity of Wikipedia made Media-Wiki syntax the de-facto
>> standard. It's not perfect, but please don't reinvent the wheel
>> (even though it's a PHP wheel).
> [..]
> Noone other than Mediawiki uses the Med
On 6/2/06, Paul Hodges <[EMAIL PROTECTED]> wrote:
Though if that works, you could squish this example even more, to
class QueueRunner {
our sub process_queue(Code @jobs_in) {
map { async { &_() } } @jobs_in;
}
}# end QueueRunner
# Elsewhere...
my @answer = QueueRunner.process
Thomas Wittek wrote:
> Where should I start, when I want to get myself a picture of the current
> Perl 6 language features and syntax?
To conclude this, I'll give a list of online docs I find interesting
about learning Perl6:
1) Synopses:
http://dev.perl.org/perl6/doc/synopsis.html
2) pugs/do
Author: audreyt
Date: Sat Jun 3 05:49:52 2006
New Revision: 9435
Modified:
doc/trunk/design/syn/S04.pod
Log:
* S04 - Change this example:
if -e { say "exists" } { extra() }
to this:
if rand { say "exists" } { extra() }
Because bare "-e" may be removed along with all $_-default
Author: audreyt
Date: Sat Jun 3 07:12:04 2006
New Revision: 9442
Modified:
doc/trunk/design/syn/S05.pod
Log:
* At scw++'s request, add an explicit definition to the default :
"\s+ if it's between two \w characters, \s* otherwise"
Modified: doc/trunk/design/syn/S05.pod
===
在 2006/6/3 下午 3:03 時，Shu-Chun Weng 寫到：
I'll then rewrite most of my rules into tokens. And about the
definition of , the "engine" I mentioned is Pugs::Complier::Rule,
so that if what PGE does is considered the "correct" way, I will
change the behavior of P::C::Rule.
Yes, please do. :-)
By
On Fri, Jun 02, 2006 at 09:35:00AM -0400, Will Coleda wrote:
> Per leo, "As of r12867 this is fixed."
Fixed for me. Thanks Leo!
Tim.
> On Jun 2, 2006, at 8:24 AM, Will Coleda wrote:
>
> >Known failures.
> >
> >Per Leo, failing tests were committed for these features to
> >"encourage" developm
Hi,
Thanks for the comments :)
I'll then rewrite most of my rules into tokens. And about the
definition of , the "engine" I mentioned is Pugs::Complier::Rule,
so that if what PGE does is considered the "correct" way, I will
change the behavior of P::C::Rule. By the way, if someone can add
it to
26 matches
Mail list logo
