RFC 186 is another interesting -io RFC, even though I'm not on the -io
list. I couldn't find any discussion in the mail archive, so here's
some to
start it. Please copy me on the discussion. Sorry for cross posting,
but
this is attempting to unify RFCs from different lists; I've bcc'd two of
th
RFC 186 is another interesting -io RFC, even though I'm not on the -io
list. I couldn't find any discussion in the mail archive, so here's some to
start it. Please copy me on the discussion. Sorry for cross posting, but
this is attempting to unify RFCs from different lists; I've bcc'd two of th
Michael G Schwern writes:
> "perl-benchmarks" good idea. Who's chairing? (not me, not now anyway)
I *strongly* recommend giving it a deadline and a specific goal. Also,
the mailing list name would be perl6-qa-benchmarks.
Nat
Here's what's going on currently as I see it (in no particular order):
JART
Embedded testing, Pod::Tests and Testing example code
Benchmarks, both big and small.
Sourceforge code repository
Black hat wearing (currently this is RFC sanity checking, pointing out
ambi
A whole bunch of non-trivial things happen to be coinciding for me in
the next two weeks, moving, YAPC::Europe, Perl 6 deadline, work
deadlines etc... and in an attempt to simplify and enjoy life
more I'd like to hand off chair of perl-qa to someone else
until the end of the month.
The basic resp
On Wed, Sep 13, 2000 at 09:18:24AM -0700, Dave Storrs wrote:
> Is it worth opening a new list, "perl6-benchmarks"? I have a
> feeling that the traffic flow could be fairly high, at least for a while.
"perl-benchmarks" good idea. Who's chairing? (not me, not now anyway)
--
Michael G Sch
On Tue, 12 Sep 2000, Michael G Schwern wrote:
> On Tue, Sep 12, 2000 at 06:56:36PM -0600, Nathan Torkington wrote:
> > I'd rather see someone write a program that involves [stuff]
>
> This is a good place to start. "Things That I'm Worried About". We
> all have our shit lists about what part
Nathan Torkington wrote:
>
> I'd rather see someone write a program that involves file reading
> and writing, regular expression manipulation, some string tweaking
> (length, concatenation, etc), and some object method calls. That
> covers the spectrum of Things That I'm Worried About.
pod2text
Michael G Schwern sent the following bits through the ether:
> The things we bench need not be simple low level bits.
AFAIK benchmarking in general hasn't really been done in Perl, apart
from the recent slew of 'sort' benchmarks. I think that proper
benchmarks give us a great deal of information
