Nicholas Clark wrote:
>
>An IRC channel is good for discussions. But it doesn't archive them,
>index them, collate them and provide them as reference for any new
>would be recruits. I'm not saying that anyone has to write the docs, or
>even the skeleton of the docs for their code - everyone and a
ive oft wondered how a constant/parameter namespace could be designed to:
- lighten Exporter symbol export in perl 5
- expose (for example) POSIX constants in only the contexts where
theyre meaningful
within a POSIX call - ex various c-open flags (im too lazy
to cite any cu
Paul Johnson wrote:
On Mon, Jul 11, 2005 at 02:54:19PM -0700, Michael G Schwern wrote:
On Mon, Jul 11, 2005 at 11:22:51PM +0200, Paul Johnson wrote:
my $foo = $bar || default(); # DC ignore X|0
"Hey, Devel::Cover! Ignore the case where the right side of this logic is
false.
pardon the lack of clue I reveal here, but..
on 32 bit box, a void* has 3 values which are illegal/unaligned;
void* ptr;
if (ptr & 0x00) {
/* ok */
} else {
/* some exceptional situation */
}
is there any concievable use of this which doesnt interfere with
legitimate bus-errors (ie exi
Dan Sugalski wrote:
At 7:35 AM -0500 12/31/02, Jim Cromie wrote:
pardon the lack of clue I reveal here, but..
on 32 bit box, a void* has 3 values which are illegal/unaligned;
void* ptr;
if (ptr & 0x00) {
/* ok */
} else {
/* some exceptional situation */
}
is there any conciev
Nicholas Clark wrote:
Admittedly my program may not be portable Ook! as it does assume that
cells wrap round from 255 to 0
The original brainfuck version worked fine on Leon's interpreter.
(I find Ook! too hard - I'm just another brainfuck monkey)
Nicholas Clark
.
I hesitate to suggest (se
Damian Conway wrote:
Can I suggest that an alternative solution might be the following:
So an L2R array-processing chain is:
@out = @a ~> grep {...} ~> map {...} ~> sort;
There might also be a be special rule that, if the RHS is
a variable, the LHS is simply assigned to it.
[EMAIL PROTECTED] wrote:
Shouldn't access to 'is computed' arrays be read-only?
If you want to be able to consume the elements by shifting,
you can always create a tied object that kees a cursor and
a reference to the underlying array and gives you that
access (and it could die for splicing, etc
Jerome Quelin wrote:
Steve Fink wrote:
I'm assuming this will be 0.0.10
codename?
I could be persuaded to call it 0.1.0
codename?
Jerome
while trolling for things parrot, I came upon this;
http://www.kingsnicknames.co.uk/
Towards the bottom of this paragraph is the HIT, from
following corrects 1 remaining use of bare 'perl' to match all the other
uses of $(PERL)
--- root.in~Sun Aug 10 15:54:44 2003
+++ root.inSun Aug 10 17:58:02 2003
@@ -480,7 +480,7 @@
cpu_dep$(O) : $(GENERAL_H_FILES)
nci.c : call_list.txt build_nativecall.pl
-perl build_nativecall.pl ca
Andy Lester wrote:
http://www.petdance.com/random/tap.html
Looks good. Thanks for working on this.
You're welcome.
Everyone: I still need more comments. Pete Krawczyk's the only one to
provide complaints yet.
The synopsis uses passive voice; <.> is called TAP.
Id turn that around.
folks,
Attached is a patch to Devel::Size which computes CV / coderef sizes.
It includes some bad/place-holder pod.
Feedback (off this list) is welcome.
tia
Jim Cromie
patch.dsize.60_06.bz2
Description: BZip2 compressed data
foo = 'baz to stdout';$/),
"auto.stdout1 has expected content");
The results suggest that the embedded tests trump the outer ones,
cuz the line-counts thru most of the module-report are 6, matching the
number of embedded $^X tests.
Is there an easy way to do what Im trying ?
tia
Jim Cromie
Sébastien Aperghis-Tramoni wrote:
Selon Michael G Schwern <[EMAIL PROTECTED]>:
On Sun, Mar 06, 2005 at 09:54:44PM +0100, S?bastien Aperghis-Tramoni wrote:
Instead of running the code on one server, where it's a problem, why
not running on machines where all prereq modules are already instal
CÃdric Bouvier wrote:
I think I will call it Run::Distributed after all.
theres also module-authors@perl.org that discusses name-space choices
regularly.
Michael G Schwern wrote:
On Mon, Mar 07, 2005 at 07:45:39AM -0700, Jim Cromie wrote:
Theres another issue: coverage can depend upon presense of other modules,
ex Test::Warnings, being installed on testers boxes, those tests would
be skipped otherwise,
and perceived coverage would suffer
Michael G Schwern wrote:
On Mon, Mar 07, 2005 at 11:24:42AM -0700, Jim Cromie wrote:
are MM or MB analyses posted anywhere for general perusal ?
Nope. You're free to run it yourself though. :)
Its likely to be pretty appauling because of all the multi-platform code and
that XS co
There is no skip_rest(), but skip_all() can do that job, with a tiny
enhancement
sub skip_all {
-if (@_) {
- print STDOUT "1..0 # Skipped: @_\n";
+if ($test == 1) {
+ if (@_) {
+ print STDOUT "1..0 \# Skipped: @_\n";
+ } else {
+ print STDOUT "1..0\n"
Jim Cromie wrote:
Rafael Garcia-Suarez wrote:
2. you gave me an idea for a Grand Plan.
Heres a 'working' version of my earlier proposal,
patched against [EMAIL PROTECTED]
I hope you find it useful for regression testing of the optimizer,
and the opcode generation phases.
1st some
Andy, etal,
Id like to propose that I (or someone like me) add a passthru option
which lets someone pass thru options and arguments to the test scripts
being run.
The idea is to support 'torture' testing as it is typically (I think)
done now.
and not coincidentally ...
[EMAIL PROTECTED] added
Andy Lester wrote:
Id like to propose that I (or someone like me) add a passthru option
which lets someone pass thru options and arguments to the test scripts
being run.
Is this better than some kind of environment variable that you set, and
that your test programs detect and use?
xoa
th
Andy Lester wrote:
thats precisely what -v does currently, same convenience argument applies.
I see a difference in that
prove -v
is shorthand for
TEST_VERBOSE=1 make test
I thought it was
"HARNESS_VERBOSE"
If true, Test::Harness will output the verbose results
Andy Lester wrote:
thats precisely what -v does currently, same convenience argument applies.
I see a difference in that
prove -v
is shorthand for
TEST_VERBOSE=1 make test
I'm not against the idea. Just not sure about the implementation.
Whyncha write the manpage docs for how it
Jim Cromie wrote:
folks,
attached patch has following adjustments to B::Concise and its tests.
heres 2nd rev of that patch, now against 22802
- crossposted to perl-qa for its test related aspects.
items 1-9 from prev post are all improved or solved
a. goto-bug squashed - reset_sequence() now
stevan little wrote:
I looked on the site (http://qa.perl.org/phalanx/), but there was
nothing said about how to get involved in this project. Are you
looking for help? And if so, how can I help?
Thanks,
Steve
sure. Pick a module from phalanx 100, based upon your personal uses,
or whichever mod
Potozniak, Andrew wrote:
Encouraging simple status reports, say monthly, may help ensure
progress.
Or...we could set some deadlines...like have 50% of your
module tested
by YAPC, and/or possibly have some incentives.
Say "..50%.. of modules tested by YAPC or we cancel the conferen
hey all,
Ive been doing hoplite type stuff on B::Concise,
so I figured Id come here, shield & spear in hand, to seek some free help.
If you build bleadperl, please apply this patch, and maybe rebuild with
-Uuseperlio.
(sh Configure -des -O -Uuseperlio) I think.
For me, the patch fixes this:
linux
stevan little wrote:
On May 7, 2004, at 1:37 PM, Tim Bunce wrote:
But still no hoplite has actually adopted the DBI...
Since I would like to get involved here, and (with the exception of
HTML::Template, which is already taken) the module I know best in the
100 is DBI. Besides, it seems like Tim
Jim Cromie wrote:
If you build bleadperl, please apply this patch, and maybe rebuild
with -Uuseperlio.
(sh Configure -des -O -Uuseperlio) I think.
never mind testing this - its now in as 22801
the rest still is open tho.
Luke Palmer wrote:
It's likely that CPAN will have a Bundle::EYEWTIBWATA. [1]
[1] Everything You Ever Wanted To Install But Were Afraid To Ask
EYEWTIBWATL eye-witty-bwattle
.. But Were Always Too Lazy
for various reasons, it would be nice to have a newsgroup,
ex this one (perl.test, but sending failed), or perhaps
[EMAIL PROTECTED], that gets full-reports for smoke-tests when
something breaks.
While I recognize that failure reports on [EMAIL PROTECTED] are
often user misconfigurations, etc,
5.8.1 recently started failing 2 tests in op/cproto.t, on pop(), shift();
this only happens on one box, ie RH-7.2, not RH-9, and I havent tried
a make distclean, so I havent reported it to p5p.
Instead I decided that some false laziness was in order, and I should go
digging.
But, I thought it wo
Dan Sugalski wrote:
Hey folks.
It's that time of year again, when the patch pumpkin passes paws. Hands,
rather. Steve Fink now joins the ranks of Parrot Pumpkings Emeritus,
having shepherded a number of releases out the door. We wish him a happy
retirement and hope the nervous twitches stop soon.
Tels wrote:
test. I know I have at least written one that did "setup and compile" some
stuff in test 00, and then runs the rest,
Theres something of a nascent convention here;
00_*.t and 99_*.t could be 'reserved' to be 1st and last
respectively, with others randomized.
begin_* and end_* ar
hi all,
im patching a module that uses Test::More, and I want to include a test
to prove that a carp is being called when function args are wrong.
I half-expected to find a stderr_like() that would do the trick.
I ended up with this;
{
local $SIG{__WARN__} = sub {
return if $_[0] =~ /follow
putting a name to it is painting a bullseye on it ;-)
I recently wrote a test to do a benchmark / performance test,
and found it somewhat difficult to get the output out to screen,
the STDOUT, STDERR takeover done by Test::More was
catching, and counting it as errors. (i think, but its not pertine
?
Im using several pieces of W3-Mech tests.
tia,
jimc
Original Message
Subject:a 3 process test for HTTP::Recorder
Date: Sat, 13 Dec 2003 22:43:10 -0700
From: Jim Cromie <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Hi Linda, HT-Proxy folks
hi folks,
I just got a CPANTS report..
I am puzzled how
5 tests could fail 10 times
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t\speed.t25
Jim Cromie wrote:
hi folks,
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t\warns.t 2 512 5 10 200.00% 1-5
You tried to plan twice! Second plan at t\warns.t line 5
It appears that this
Andy Lester wrote:
It appears that this doesnt error on 5.8.2, but is repeatable on 5.00503,
as follows:
I don't see any problem here. You can't have more than one plan.
xoa
The different Version responses threw me.. I worked out a way...
use Test::More;
use Benchmark();
plan skip_a
Fergal Daly wrote:
NAME
Test::Benchmark - Make sure something really is faster
SYNOPSIS
is_faster(-10, sub {...}, sub {...}, "this is faster than that")
is_faster(5, -10, sub {...}, sub {...}, "this is 5 times faster than that")
is_n_times_faster(5, -10, sub {...}, sub {...}, "t
Fergal Daly wrote:
On Wed, Dec 17, 2003 at 09:28:48AM -0700, Jim Cromie wrote:
Hi Fergal,
Id like to see a slightly different interface:
is_faster( sub{}, sub{}, "1st is faster");
This would be nice but what value should I use for iterations? I suppose -1
Benchmark defa
Andy Lester wrote: wrt RGS feedback,
I don't get the rationale for this change; diag() is supposed to be
used for error/diagnostic messages, right ? not for comments, more
mundane in nature. (This perturbs the nice line-up of my test logs.
Go ahead and patch it. I'll add an "unless $ENV{PER
Rafael Garcia-Suarez wrote:
Jim Cromie wrote:
Well, it seems Ive been abusing diag() for some time now :-O
Is there a 'right' way to do this ? perhaps just using ok() ?
ok() goes to stdout by default, diag() to stderr
which is, I presume, why perl -Ilib t/foo.t produces m
Ruslan U. Zakirov wrote:
Hello, all.
I have several questions about multiply perl versions.
Im not sure this Q is on-topic, but here goes.
(btw, its multiple, as in many, not multiply, as opposite of divide)
1) I have got RH9 and FreeBSD and when I was setting up perl5.8.1
script ask me "
Folks,
I hope this is an appropriate forum, I want to get the topic off of p5p,
and return there later with a more polished solution...
Rafael Garcia-Suarez wrote:
jim cromie wrote:
I picked this back up recently, I think it now incorporates all comments
from this thread started 1/6/04, plus a
Rich Morin wrote:
> At 11:24 PM -0500 3/6/02, Uri Guttman wrote:
>
>> qn would be just like qq but not allow any
>> direct hash interpolations (%foo or %foo{bar}). you can always get those
>> with $() if needed. this solves the common case with a minimal of noise
>> and the uncommon case h
so, assuming we have;
print 'you gave me: @wordlist = ';# single quote - no interpolation
for @words -> $it {
print;
FIRST { print '(' }# provisionally
NEXT { print ',' }
LAST {print ');' }
}
# and maybe
else {
print "();\n";
}
this yields:
you gave me: @wo
Dan Sugalski wrote:
> At 1:07 PM -0400 4/30/02, Miko O'Sullivan wrote:
>
>> > Damian, now having terrible visions of someone suggesting
>> C ;-)
>>
>> Then may I also give you nightmares on: elsdo, elsdont, elsgrep,
>> elstry ...
>
>
> Has anyone brought up elselse or unlessunless yet?
>
and
Damian Conway wrote:
>Luke Palmer wrote:
>
>>Ooh! Why don't we have a dont command! With several variants:
>>dont FILE
>>dont BLOCK
>>
>>dont { print "Boo" }
>>
>>Would print:
>>
>>
>
>You really *should* be more careful what you wish for Luke.
>The following was just uploaded to
with p5, Ive often written
eval {} or carp "$@ blah";
it seems to work, and it reads nicer (to my eye) than
eval {}; if ($@) {}
but I surmise that it works cuz the return-value from the block is non-zero,
for successful eval, and 0 or undef when block dies, not cuz of magical
treatment of $@
perl5 has a facility to dump the optree in XML,
which is currently not regression tested.
Ive submitted a test-file which tests the XML output
against a few golden-samples, but its been ignored/overlooked.
So let me ask:
is MAD XML output used in any way currently (or in future) ?
is there a
On Mon, Aug 10, 2009 at 10:31 AM, Carl Mäsak wrote:
> In my post "Three things in Perl 6 that aren't so great" [0], I
> outline three things about Perl 6 that bug me at present. Commenter
> daxim made what seems to me a sensible proposal [1] for solving the
> third problem, "Comments in the begin
On Tue, Aug 11, 2009 at 8:59 AM, Jon Lang wrote:
> Ben Morrow wrote:
> > However, I would much rather see a general syntax like
> >
> >(# ... )
> >{# ... }
> >[# ... ]
> >
>
a preceding ':' (colon) makes it *notionally*
a null-label-block-comment-construct.
>
> > with no whitespace
54 matches
Mail list logo
