"Jonathan Scott Duff" <[EMAIL PROTECTED]> wrote:
On Thu, Jun 01, 2006 at 02:22:12PM -0700, Jonathan Lang wrote:
Forgive this ignorant soul; but what is "STM"?
Software Transaction Memory
Well, Software Transactional Memory if I'm being picky. :-) Some info and
an interesting paper here:-
Hello,
(used to post on google group but found it does not deliver)
I'm implementing "MiniPerl6" in pugs which is the first step of
writing perl 6 parser in perl 6. In module Pugs::Grammar::MiniPerl6,
http://svn.openfoundry.org/pugs/misc/pX/Common/Pugs-Grammar-MiniPerl6,
I use another perl 6 gr
> > James Mastros wrote:
> > > I don't like the name synchronized -- it implies that multiple
> > > things are happening at the same time, as in synchronized swiming,
> > > which is exactly the opposite of what should be implied.
> > > "Serialized" would be a nice name, except it implies serializ
The note below is in reply to these preceding posters:
> From: Ovid [mailto:[EMAIL PROTECTED]
[...]
> From: Ask Bjørn Hansen [mailto:[EMAIL PROTECTED]
[...]
> From: Fagyal Csongor [mailto:[EMAIL PROTECTED]
[...]
> From: [EMAIL PROTECTED]
[...]
Thanks for the thought-provoking comments and suggest
At 12:00 on 06/01/2006 BST, David Cantrell <[EMAIL PROTECTED]> wrote:
> Basic I/O is talking to filehandles and nyetwork sockets. Anything
> above the UDP / TCP level should not, IMO, be included.
I'd respectfully disagree. Just like text isn't just ascii any more,
content isn't just on local
On 01/06/06, Josh Wilmes <[EMAIL PROTECTED]> wrote:
At 12:00 on 06/01/2006 BST, David Cantrell <[EMAIL PROTECTED]> wrote:
> Basic I/O is talking to filehandles and nyetwork sockets. Anything
> above the UDP / TCP level should not, IMO, be included.
I'd respectfully disagree. Just like text isn'
# New Ticket Created by Tim Bunce
# Please include the string: [perl #39255]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39255 >
---
osname= darwin
osvers= 8.0
arch= darwin-thread-multi-2level
cc= cc
---
Flags:
* Michael Mathews <[EMAIL PROTECTED]> [2006-06-02 12:10]:
> I would also point to PHP's fread() (and friends) functions,
> which take "filenames" in the form of "C:\\blah" or
> "http://foo.com/blah"; and behaves the same.
Yes, which means that any un- (or badly) sanitised user input has
the potent
Known failures.
Per Leo, failing tests were committed for these features to
"encourage" development.
We've tried to let head be usable for this long, we should probably
have some kind of procedure for dealing with this this sort of
development to avoid this sort of confusion.
Thanks for
Am Mittwoch, 31. Mai 2006 19:40 schrieb Will Coleda:
> #39254] Unicode sub names don't work with :multi
As of r12867 this is fixed.
All tests successful again, which means, we need more tests.
leo
On 02/06/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
* Michael Mathews <[EMAIL PROTECTED]> [2006-06-02 12:10]:
> I would also point to PHP's fread() (and friends) functions,
> which take "filenames" in the form of "C:\\blah" or
> "http://foo.com/blah"; and behaves the same.
Yes, which means that
--- John Drago <[EMAIL PROTECTED]> wrote:
> > You mean "is parallel" as a synonym for "is async"?
>
> I think "is parallel" denotes something as usable by multiple threads
> simultaneously, "in parallel".
> "is serial" would denote that only one thread can use the $thing at a
> time, exclusively
On Fri, Jun 02, 2006 at 02:17:25PM +0800, Shu-chun Weng wrote:
> 1. Spaces at beginning and end of rule blocks should be ignored
> since space before and after current rule are most likely be
> defined in rules using current one.
> 1a. I'm not sure if it's "clear" to define as this, but t
Per leo, "As of r12867 this is fixed."
On Jun 2, 2006, at 8:24 AM, Will Coleda wrote:
Known failures.
Per Leo, failing tests were committed for these features to
"encourage" development.
We've tried to let head be usable for this long, we should probably
have some kind of procedure for d
On Jun 1, 2006, at 11:37 AM, Josh Wilmes wrote:
At 12:00 on 06/01/2006 BST, David Cantrell <[EMAIL PROTECTED]>
wrote:
Basic I/O is talking to filehandles and nyetwork sockets. Anything
above the UDP / TCP level should not, IMO, be included.
I agree.
I'd respectfully disagree. Just l
* Michael Mathews <[EMAIL PROTECTED]> [2006-06-02 15:25]:
> I believe I said "in Perl6 modules" not "in the language core"
> as you imply
My apologies; I misremembered the argument, and the PHP example
you gave only happened to reinforce my misconception.
I agree then; having clients for a few ne
> > > You mean "is parallel" as a synonym for "is async"?
> >
> > I think "is parallel" denotes something as usable by multiple threads
> > simultaneously, "in parallel".
> > "is serial" would denote that only one thread can use the $thing at a
> > time, exclusively.
>
> Are you saying both are as
At 1:50 PM -0700 6/1/06, Larry Wall wrote:
As for side-effecty ops, many of them can just be a promise to perform
the op later when the transaction is committed, I suspect.
Yes, but it would be important to specify that by the time control is
returned to whatever invoked the op, that any side
Hi all,
Coke suggested to create a map with people working on Parrot.
Create the map in Frappr.
The URL is:
http://www.frappr.com/parrotcoders
Feel free to add yourself
Cheers
Alberto
--
Alberto Simões - Departamento de Informática - Universidade do Minho
Campus de
Hi
I am toying around with Parrot and the compiler tools. The documenation
of Perl 6 grammars that I have been able to find only describe rule. But
the grammars in Parrot 0.4.4 for punie and APL use rule, token and regex
elements.
Can someone please clarify the difference between these three
On 6/2/06, Rene Hangstrup Møller <[EMAIL PROTECTED]> wrote:
Hi
I am toying around with Parrot and the compiler tools. The documenation
of Perl 6 grammars that I have been able to find only describe rule. But
the grammars in Parrot 0.4.4 for punie and APL use rule, token and regex
elements.
Can
# New Ticket Created by Will Coleda
# Please include the string: [perl #39272]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39272 >
Some of these tests are failing. I can't isolate a small test case,
but here's the las
--- John Drago <[EMAIL PROTECTED]> wrote:
. . .
> > class QueueRunner {
> >our sub process_queue(Code @jobs_in) {
> > my @ans is serial;
> > @ans.push map { async { &_() } } @jobs_in;
> > @ans;
> >}
> > }
> > my @answer = QueueRunner.process_job_queue( @jobs );
>
> Actual
On Fri, Jun 02, 2006 at 01:56:55PM -0700, jerry gay wrote:
> On 6/2/06, Rene Hangstrup Møller <[EMAIL PROTECTED]> wrote:
> >I am toying around with Parrot and the compiler tools. The documenation
> >of Perl 6 grammars that I have been able to find only describe rule. But
> >the grammars in Parrot 0
Patrick R. Michaud wrote:
Jerry is correct that S05 is the place to look for information
on this. But to summarize an answer to your question:
Thank you very much for the swift and thorough answer. It answered all
my questions. Your reply was very pedagogical and deserves to go into
the man
We are trying to use Devel::Cover module and "cover"
in our regression tests run to generate product code
coverage data. However, we met two big problems:
(1) Lots of our perl test scripts failed in code
coverage run and seems related to B::Deparse and we
got million lines of messages like below i
Scott Wang wrote:
We are trying to use Devel::Cover module and "cover"
in our regression tests run to generate product code
coverage data. However, we met two big problems:
(1) Lots of our perl test scripts failed in code
coverage run and seems related to B::Deparse and we
got million lines of m
27 matches
Mail list logo
