On Fri, May 13, 2005 at 03:00:39PM +1000, [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
>
> >Covering the XS portion of the code with gcov is possible, and Devel::Cover
> >will create all kinds of nice webpages and statistics for you too.
> >Paul Johnson
at the moment, I'm afraid.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
he scalar context is an RFC valid string. Nothing too heavy
there. The time() function is "typically" only moderately useful without
localtime().
Paul
ck there at all, so that suggests something
> funny is going on.
Certainly. Of course, it's always possible and quite likely that there
is a bug in my code somewhere. But there is also a chance that I am
conflating two ops, since I have yet to come up with a way to uniquely
identify an op (suggestions welcome). You're not running on 5.6.x are
you?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
hanges are between 5.8.0 and 5.8.1, but I notice the docs
are wrong there. They wont be in the next release.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
d only be for the
benefit of people and modules that mess with the op tree. Again, I
submit that an optimisation that changes normal behaviour is broken and
that, in general, programmers shouldn't need to worry about what
optimisations are going on under the covers.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
7;t even convince them to install a modern
> Perl in a separate location and leave the old code running 5.5.3.
I've just been through the should-I-shouldn't-I-support-5.4 with my
(painfully slow) rewrite of Compress::Zlib. In the end I included limited
sup
usands of machines in dozens of different
configurations function at least as well as they did before is a little
harder.
And whilst I know how to manage all this, sometimes it's hard enough
just stopping people from mandating the use of ksh, Java and XML.
Having said all that, feel free to do what you want with 5.004 support.
I don't care! I have 5.005!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
a beta on CPAN, I'd prefer
it doesn't get used in anger until it has bedded-in. If I give the module a
version number like 2.000_00, will the CPAN shell ignore it?
Paul
___
How much free photo storage do you get? Store your holiday
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
ays thought that Compress::Zlib is just a wrapper around zlib which
> in
> > turn is C and developed elsewhere (and in stable state for a long time
> now).
> >
> > What is "(painfully slow) rewrite"?
>
> I think Paul means that it is taking him a long
From: Paul Johnson [mailto:[EMAIL PROTECTED]
> On Mon, Jul 04, 2005 at 03:00:14AM -0700, Michael G Schwern wrote:
>
> > On Mon, Jul 04, 2005 at 10:36:39AM +0100, Ben Evans wrote:
> > > I would say that this cascade effect is precisely why you *should*
> > > dro
From: Yitzchak Scott-Thoennes [mailto:[EMAIL PROTECTED]
> On Mon, Jul 04, 2005 at 02:19:16PM +0100, Paul Marquess wrote:
> > Whilst I'm here, when I do get around to posting a beta on CPAN, I'd
> prefer
> > it doesn't get used in anger until it has bedded-in. If
On Wed, Jul 06, 2005 at 01:36:10AM +0200, Abigail wrote:
> On Mon, Jul 04, 2005 at 05:21:01PM +0200, Paul Johnson wrote:
> >
> > Unfortunately, upgrading isn't always an option. Anyone can type
> >
> > $ ./Configure -des && make && make test in
; # from the end backwards 10
$fh.seek(10, :relative); # from the current location forward 10
$fh.seek(-10, :relative); # from the current location backward 10
Paul
nsion also to say
$fh.pos += 10`bytes
as shorthand for
$fh.pos = $fh.cur + 10`bytes
Likewise for -=
But then that begs the questions of *= (not too nuts), /= (same),
%= (great for fixed length records?) and the predictable other ho
nd even tests inline, which tells me that I
really should be ignoring their opinions, but I try to please my users
anyway, and so I'll see what I can do.
> Ignored conditions would be green, but perhaps a slightly different shade of
> green so they can be spotted if you're lookin
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 thi
ult to the invocant ($_ =:= $?SELF) (which should be easy enough with
"method a ($_) { ... }").
method concrete {
./wizbang;
.foo for @.elems;
.foo for ./elems; # possibly odd looking - but not confusing
}
Please, lets pick something sane. Here I go speaking for the list, but I
don't think we will find many that think ".method syntax breaks in methods if
$_ is rebound" as a very sound concept.
Paul
irtual ($obj.y)
has %.y is rw; # implies %_y for storage, is virtual
Paul
ta => [$up, $right]);
OR assuming I has a Position object and a vector object
move(from => $pos1, delta => $vec1);
The original example just seems difficult to parse.
Paul
n my local configuration.
>
> The Test::Builder::Tester distribution includes
> Test::Builder::Tester::Color. That might be useful - or might serve as a
> good basis to build something on.
See also Apache::Test.
http://perl.apache.org/docs/general/testing/testing.html#Colored_Trace_Mode
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
is big enough - 512M might still be enough. See
http://www.perladvent.org/2004/5th/
Do the same when you need to upgrade something.
I managed to install svk and a bunch of other stuff in this fashion
without problem.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
olkit.
>
> yah, this is a bit more complex than it probably ought to be, but I guess
> that's by design. it could also be a bit better documented, but...
...
> IIRC paul had some info on this at his YAPC::EU advanced Devel::Cover talk
> (which I did not attend) so maybe he
g small, self contained test
cases, go a long way to helping such problems get solved ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
est basing your work on cpancover in the Devel::Cover
distribution. (I think I have mentioned this before.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, May 13, 2005 at 05:18:40PM +0100, Tim Bunce wrote:
> On Fri, May 13, 2005 at 10:51:56AM +0200, Paul Johnson wrote:
> > On Fri, May 13, 2005 at 03:00:39PM +1000, [EMAIL PROTECTED] wrote:
> >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > >Cov
ns.
I may yet completely overhaul the option handling. That this is a
possibility is the major reason I still call the code alpha.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, Nov 04, 2005 at 11:02:42AM -0500, Will Coleda wrote:
> The mail list strips out .t attachments (Robert? is this necessary?)
This was changed on perl5-porters a few weeks ago, and since then I
don't recall seeming a marked increase in troff spam.
--
Paul Johnson - [EMAIL PROTECT
On Mon, Dec 02, 2002 at 01:58:11PM -0800, Dave Whipp wrote:
> At various times, I have seen proposals for using indentation with HERE
> docs. Was this issue ever resolved?
RFC 111 - Apo 2 - accepted.
Keep up at the back there :-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
> Or what?
How about the same way as one would do it now? Presumably we won't all
forget how to program when Perl 6 comes out.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Mon, Dec 09, 2002 at 02:20:01PM -0800, Austin Hastings wrote:
>
> --- Paul Johnson <[EMAIL PROTECTED]> wrote:
> > On Mon, Dec 09, 2002 at 01:58:11PM -0800, Austin Hastings wrote:
> > > Ahh. This is better. How does one implement a more sophisticated
>
y
and follow them up in makeshortlink. Can I just get your summary and
drop the rest of the subscription?
Paul Kienzle
[EMAIL PROTECTED]
Perhaps a future implementor of the matlab interpreter in parrot.
ood.
When I later saw it using mutt in an xterm, the tilde was at the top of
the character, where I was more used to seeing it and it didn't look like
an arrow any more, nor did it look very good to me.
This is the way it looks on my browser ~>
When I get home I'll mail a messa
On Fri, Jan 10, 2003 at 03:55:30PM -0500, Andrew Rodland wrote:
> On Friday 10 January 2003 11:42 am, Paul Johnson wrote:
> > Damian Conway said:
> > > Andy Wardley wrote:
> > >> The arrow is a special case. I don't read that first character
> > >> a
n change for its own sake.
> I have to wonder how many people actually like this syntax, and how many
> only say they do because it's Damian Conway who proposed it.
I trust that we are all sufficiently grown up and devoid of marketing hype
that we can judge suggestions on their own merit.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
h
> funding Dan was in fact supporting the much broader benefits of Parrot
> development and funding me probably benefitted Perl 5 even more than Perl
> 6).
Well, I'll be pretty interested to discover what cause is deemed more
deserving than Larry, Perl 6 or Parrot. The P still
the companies who are
(hopefully) making a profit on the backs of those projects. Yes, I know
it's not that easy.
No one's job depends on Perl 6 or Parrot (yet). Well, hardly anyone's :)
Still, I suppose I am preaching to the choir in the wrong chapel.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sat, Jan 18, 2003 at 02:11:37AM +, Simon Cozens wrote:
> [EMAIL PROTECTED] (Paul Johnson) writes:
> > That may well be true, but it seems to me that if people's jobs depend
> > on those projects then there is (or could be or should be) a source of
> > funding
; my @a is Array( default => { $_ ** 2 });
>
> STRAWMAN ANSWER: Yes, because it's cool.
No, because it's unnecessary. You can always do
my $value = @a[$x] //= $x ** 2;
or skip the = depending on how you are trading memory / speed.
Yes, I know that just about every
03-01-28 at 14:47, Paul Johnson wrote:
> > Michael Lazzaro said:
>
> > > 2a) When a cell is explicitly re-undefined, does the default value take
> > > effect?
> > >
> > > my @a is Array( default => 'foo' ) = (1,2,3);
&g
27;sub e { print exists $a[shift] ? 1 : 0 } e 2; $a[4]++; e 2; e 4; delete
$a[4]; e 2; e 4'
0
0
1
0
0
No, I don't know which side I'm arguing anymore :-)
Actually, I do. I don't like exists on arrays.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ays to be undef. Both
approaches can also be extended to hashes.
I think the question of what to do with int arrays is somewhat separate.
Might I suggest that storing undef in an int array is not appropriate,
and thus having a (user defined) default value in an int array is also
not appropriate. If you
rge together. If it's Wednesday it must be Zurich. We
enjoyed you being here even if you can't remember it ;-)
Oh well, it was only two letters. There wasn't anything about
approximate matching in A5, was there?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
'
It's alright. It works just fine as a module. I think Parrot even has
an appropriate opcode.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
e of the left to right ordering.
For example,
select((select(OUTPUT_HANDLE), $| = 1)[0]);
which is (was?) a fairly common idiom, is documented, used in core
modules and tested. I suspect that a lot would break if the order of
evaluation changed. And I think it would be sensible for Perl 6 to
define such an order.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Hi,
Attached is a patch to make examples/assembly/cat.pasm terminate when it
receives a ctrl-D. I'm new to the list and to Parrot, so please be
gentle if I've committed some sort of faux pas :).
--
Paul Duncan <[EMAIL PROTECTED]>pabs in #ruby-lang (FN IRC)
http://w
look at the recent p6i archives for the gory details.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Brian Wheeler <[EMAIL PROTECTED]> writes:
> Any thoughts?
Are you running RHL 9? If so, unset LANG and try rebuilding.
Default RHL 9 w/ LANG="en_US.UTF-8":
$ make jit_cpu.c
/usr/bin/perl jit2h.pl i386 jit_cpu.c
jit2h: 1 (+ 177 vtable) of 1050 ops are JITed.
and with unset LANG...
$ rm jit_cp
he best way to handle all Devel::Cover's tests now
failing.
I'd welcome any feedback and ideas for improvements.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
S.
My personal itch that this would scratch is to be able to specify
prerequisites if they can be easily satisfied, and just to output a
message if the installation is manual and the prerequisites are not
essential. (Yes, I know that doesn't make sense.)
--
Paul Johnson - [EMAIL PROT
ance it would be
> accepted,
The way I deal with this is to make a module that does all the heavy
lifting, give it an appropriate import sub, and then a test reduces to
something like:
use TestX ( opt1 => "x", opt2 => "y" )
That covers everything except the perl switches, but although I've never
needed that functionality, I suppose it could be quite important.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sun, Jul 13, 2003 at 04:13:07PM +0100, Fergal Daly wrote:
> On Sunday 13 July 2003 15:53, Paul Johnson wrote:
> > The way I deal with this is to make a module that does all the heavy
> > lifting, give it an appropriate import sub, and then a test reduces to
> > something
fixes
- ... and many more
It should be on CPAN now, or get it from my homepage if you have a slow
mirror.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
self = shift;
> > $self->depends_on('build');
> > system qw( rm -rf cover_db );
>
> Not very portable :)
"cover -delete" would be the recommended way to do that. Portable, and
should still work when/if the database format changes.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
sed in the
latest release, and what isn't is on the TODO list.
> In the README:
>
> Requirements:
> - Perl 5.6.1 or 5.7.1.
> * May be 5.8.0|1 ? ;-)
> * Or 5.6.1 or greater ?
Actually, it was that way because 5.7.0 was not up to the job, and 5.8.0
didn't exist.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Tue, Sep 02, 2003 at 01:43:06PM +0200, Paul Johnson wrote:
> I've finally found no compelling reasons not to release Devel::Cover
> 0.21.
And hot on its heels comes 0.22.
This is a bugfix release. The first line of DESTROY blocks and overload
subs (and possibly some other thin
bug in this area which first appeared in
perl-5.8.3. Which version are you using? Still redhat's dodgy 5.8.0?
http://www.nntp.perl.org/group/perl.perl5.porters/85930?show_headers=0
(I meant use_ok in that message, not isa_ok.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Sat, Nov 13, 2004 at 12:33:01PM +1100, Leif Eriksen wrote:
> First, thanx so very much for responding so quickly...
That was just to make up for the short delay here, and the much longer
delay to your last mail to me ;-)
> Paul Johnson wrote:
>
> >On Sat, Nov 13, 2004 at 1
Windows but not on Darwin?
Normally they would not be covered by default, being core modules. Is
it possible that your perl is in a different location from that with
which the ppm was created?
When Devel::Cover runs it will tell you which directories are being
ignored by default. See the documentation to alter this if it is wrong
for you. (Or manually hack Devel::Cover::Inc, but that's not a
supported solution.)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
this is not
covered and this is the reason why".
> Morale - clean up and try from scratch before hitting the 'emergency
> email support' button.
>
> Thanx so much for your patience Paul - if your ever in Melbourne, I owe
> you a few shouts at the bar - I recommend a James
tters."
>
> I'd like to be able to s/Python/Perl 6/ above, but after many discussions on
> this topic, I'm still not sure if I can.
http://www.nntp.perl.org/group/perl.perl6.language/9576
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
rning a status or dying or
something. Or do it via OO. Or whatever.
Doing something similar before the test is run seems useful too.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
he regex engine and trying to do this, but to be
> honest I don't really see it happening for me. So, I figure the next
> best thing is to throw this idea out here and see if anyone else runs
> with it.
Micheal suggested mjd's Rx might be useful. Jeff Pinyan's
Re
get a coverage report about it. Which is normally fine,
since you don't want one anyway, and even if you did you couldn't
because Devel::Cover uses Storable internally.
Whether this is related to your main problem I can't tell, though I have
have seen that warning plenty of times before but never encountered your
main problem.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
tain that there's not another version of Storable
around which could be being picked up? Maybe you could try printing out
the version of Storable being used before nstore is called?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
the quoting and
attributions. s/le/wle/ gives the hint too.
Mike is quite right of course. And the code which handles this is one
of the more simple parts of perl5. Provided you're not too worried
about what's going on under the macros, I suppose.
if (SvTRUE(left) != SvTRUE(right))
RETSETYES;
else
RETSETNO;
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
--- David Storrs <[EMAIL PROTECTED]> wrote:
> . . . .
> Obviously, however @Larry decide it should be, is the way it'll be
> and nothing I can say will change that.
Au contraire -- that's what this list is for.
State your opinion, man! :)
> That said: this would suck. Badly.
> We should not be
ting_here)
I've checked that in to my development copy along with a test case based
on your failing example (I removed the rand part). If things are OK for
you I'll release a new version with this fix soon.
Thanks for the minimal test case. Bug fixes are so much easier with a
concise way to r
. Unfortunately, this
also has the effect you have noticed. B::Deparse has options to control
how the output is displayed, but I wasn't able to find anything that
improved on the current output in the general case.
I suppose that's the price you pay for TIMTOWTDI.
[ Is that a Python prog
.module, TOPs);
NDEB(D(L, "require %s\n", SvPV_nolen(MY_CXT.module)));
break;
}
Thanks for the report and sorry for the delay fixing it, and that you
needed to provide a workaround.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
ngs posted on cpan.org right next to the usual
> >>test results?
> >
> >It still chokes on certain not uncommon constructs like threads.
> >
> On that note, is forking also problematic?
Forking should be fine, for certain definitions of fine.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
=> 't/emulate.t',
>'1110216226.25105.54436' => {
> 'run' => 't/01_use.t',
>'1110216262.25141.01103' => {
> 'run' => 't/twoObjects.t',
>'1110216265.25143.07361'
On Mon, Mar 07, 2005 at 10:33:11PM +, Nicholas Clark wrote:
> On Mon, Mar 07, 2005 at 07:59:40PM +0100, Paul Johnson wrote:
>
> > To do it properly it would need to be on a machine somewhere which would
> > accept uploaded coverage databases from anyone who wanted to subm
to that which ran gcov2perl?
Other than that, I'm not sure what to suggest. If you can send me
enough to reproduce the problem I'd be glad to look into it.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
hould work on the invocant period - it just happens to be a
coincidence that $_ is the same as the invocant for most of the time.
Paul Seamons
I'll go back to lurking about now.
> eval read :file("foo")
How about:
eval slurp "foo";
Paul Seamons
gy behind the module - I'll just install it and run it.
This argument can also be applied to (most of) the modules in the Tie
namespace, though I know that not everyone is of the same opinion in
this regard.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
o determine the value of an arbitrary boolean expression
I can probably go into nauseating detail on any of these points if
required.
If you've got this far, thanks for listening!
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
On Fri, Apr 01, 2005 at 01:47:36PM -0600, Walter Goulet wrote:
> Finally, I wanted to confirm an assumption: I can split test.pl into a
> set of seperate t/*.t test scripts regardless of whether I'm using
> Test or Test::More.
Yes. Or neither or both.
--
Paul Johnson - [EMAIL P
est script tweek-then-foo.t which tweeks the system and then ensures
> that foo.t still passes. How do I write tweek-then-foo.t?
I would do it in the same way as if this had nothing to do with tests.
That is, abstract away the common code into a module, which can also
live under t/
--
Paul Jo
I would think that :p5 should behave as perl5 does by default. That would
mean that /x and /s aren't on by default (for p5).
As this is my first post about pugs - all I can say is "wow." It is great to
already be coding perl6.
Thanks Autrijus and crew.
Paul
On Thursday 14 A
27;
# prints 2 - 2 (as it should. It seems that statement modifiers don't
currently work with declarations - but that is a compiler issue - not a
language issue.)
I have wanted to do this in Perl5 but couldn't but would love to be able to do
in Perl6:
my %h = ;
{
temp %h{$_} ++ for %h.keys;
%h.say; # values are incremented still
}
%h.say; # values are back to original values
Paul
On Friday 15 April 2005 11:57 am, Juerd wrote:
> Paul Seamons skribis 2005-04-15 11:50 (-0600):
> > my %h = ;
> > {
> > temp %h{$_} ++ for %h.keys;
>
> Just make that two lines. Is that so bad?
>
> temp %h;
> %h.values ยป++;
>
For the given exa
work in Perl6 (temp $var = $var doesn't work in Perl6) and
again it may be fine for small hashes with only a little data - but for a
huge hash (1000+ keys) it is very inefficient.
This is good discussion - but it isn't the real focus of the original message
in the thread - the question is about the local (temp) scoping of looping
statement modifiers in Perl6.
Though, I do appreciate your trying to get my example working as is.
Paul
in a local. That is great!!!
Thank you very much! Wish I'd know about that three years ago.
But, it still doesn't answer the original question about scoping in the
looping statement modifiers.
Paul
hich is hidden but still retains its
contents).
Paul
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 15, 2005 at 11:28:31AM -0500, Rod Adams wrote:
> : David Wheeler wrote:
> :
> : >But the first person to write <[a...]> gets what's comin' to 'em.
> :
> : Is that nothing (since '.' lt 'a'), or everything after 'a'?
>
> Might as well make
--- Larry Wall <[EMAIL PROTECTED]> wrote:
. . .
> <-[a..z]>
>
> should be allowed/encouraged/required. It greatly improves the
> readability in my estimation. The only problem with requiring .. is
> that people *will* write <[a-z]> out of habit, and we would probably
> have to outlaw the
--- David Christensen <[EMAIL PROTECTED]> wrote:
> I'm looking in S09, and reading about junctions. It seems to me
> that if we have a junction $j which we use to index into an array
> or a hash, it should DWIM and return a junction of the corresponding
> values.
>
> @ar=[1..10];
> %hash=(a=>1,b
ogram Perl
as if it had sequence points and undefined behaviour. This often
results in explaining what they are, but maybe that's not such a great
problem.
See http://www.eskimo.com/~scs/C-faq/faq.html, especially sections 3.8
and 11.33 for details.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
nt topic. $_ defaults to the invocant of the method. $^1 refers to the
first invocant. $^ is an alias for $^1. $^n refers to the nth invocant.
Nice and simple. No conflict with existing naming conventions.
Paul
hat
code to bind the variable? I'm lazy. The signature wouldv'e been shorter.
That looks Perl5ish.
> Three, even:
Same argument as the last with a different "aliasing."
Yes, I know there "can be" a "way back." In this thread, none of the examples
give one using existing Perl 6 syntax. They are all proposing new ways.
This is one more.
Paul
Paul Seamons wrote:
> Yes, I know there "can be" a "way back." In this thread, none of the
> examples give one using existing Perl 6 syntax. They are all proposing new
> ways. This is one more.
Sorry if this sounded brash. I have a habit of not figuring out that
> dup short and long names is a waste, since people will always chose the
> short one (who uses English in Perl 5, really?)
That is the goal - to find some nice variable that looks vaguely usable and
that people won't rebel against using.
Paul
t since then it would seem that for
some strange reason more people have been exposed to functional
programming.
http://www.mail-archive.com/perl6-language@perl.org/msg11967.html
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Minor note.
Would you want this:
>sub &infix:(Str $a, Str $b) { return ($a eq $b) ? $a : ''; }
to be:
sub &infix:(Str $a, Str $b) { return ($a eq $b) ? $a but bool::true:
''; }
(Is that the right way to do it ?)
Paul
Using Test::More, I would like to send some diagnostics to be seen only
when the harness is running in verbose mode.
There doesn't seem to be a way of doing this. The best I could come up
with is:
sub vdiag { pass("@_") }
but this has little to recommend it.
Thoughts?
-
On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote:
> On 28 Apr 2005, at 14:23, Paul Johnson wrote:
>
> >Using Test::More, I would like to send some diagnostics to be seen only
> >when the harness is running in verbose mode.
> [snip]
>
> diag "s
ect - or will they cause the
quantified subrule or subpattern to return as an array of C objects?
Paul
nding that supporting 5.6
is taking a lot of time that I would rather be spending on other things.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
301 - 400 of 1010 matches
Mail list logo
