Re: New version of Perl6::Perldoc uploaded

2007-04-26 Thread Agent Zhang

On 4/25/07, Damian Conway <[EMAIL PROTECTED]> wrote:

Perl6::Perldoc v0.0.5 just hit the CPAN.



I think you have forgot to update the version number in
Perl6::Perldoc::Parser. It's still v0.0.1:

http://search.cpan.org/src/DCONWAY/Perl6-Perldoc-v0.0.5/lib/Perl6/Perldoc/Parser.pm

See line 7:

   use version; our $VERSION = qv('0.0.1');

I'd like to say something like "use Perl6::Perldoc::Parser 0.05"
because smartlinks.pl in the Pugs repos is using a feature that only
exists from v0.0.5.

Thanks, agentz


Re: New version of Perl6::Perldoc uploaded

2007-04-26 Thread Agent Zhang

On 4/25/07, Damian Conway <[EMAIL PROTECTED]> wrote:

Perl6::Perldoc v0.0.5 just hit the CPAN.

Apart from several important bug-fixes, notable new features include:



For another issue, I see diakopter++ has committed the source of
Perl6::Perldoc from CPAN to the Pugs SVN repos. Will you commit future
changes there?

If not, sync'ing two different versions will be a pain and I think we
should remove it from the Pugs tree.

And...when will S26 be committed to the synopsis repos? The latest
version of S26.pod6 seems to be bundled with the latest CPAN release
of Perl6::Perldoc, which is a bit hard to sync too. :(

Cheers, agentz


Re: [svn:perl6-synopsis] r14376 - doc/trunk/design/syn

2007-04-26 Thread Charles Bailey

On 4/24/07, Larry Wall <[EMAIL PROTECTED]> wrote:


On Tue, Apr 24, 2007 at 06:45:12PM -0400, Charles Bailey wrote:
: On 4/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
: >Note that unless no longer allows an else
: It's probably that I'm just having another day where skull > brain, but
I'm
: not sure I see the benefit to the language here.
:
: I think of "unless" as an alternate spelling for "if not", so it seems
: natural that it be possible to follow it with an "else".  I'll grant
that
: the (common) idiomatic usage of "unless" doesn't include an "else", but
that
: seems more an argument not to use an "else" rather than to forbid
it.  It's
: a bit like saying one can "continue" after a "while" but not an "until".
:
: Is there a parsing advantage that I've missed, or does it disambiguate
some
: other construct?

Yes, it's slightly easier to parse this way, and yes, it bugs me that
unless/else is not English, but mostly I changed it as a not-so-gentle
prod towards refactoring, based on the notion that if you have to
install a guard on a storage location being false, you've probably
got the scope of the storage location wrong.  And even if not, there
are several other ways to write it, at least one of which will be
generally more readable to other people.

I freely admit that it's less orthogonal and that I'm being high-handed.
:)



For situations such as this we have Rule One.

But I think I'd still ask you to reconsider, in a low-priority thread
somewhere.

My sense is that the driving consideration is more a use case than an
intrinsic element of language structure (to the extent that the two are
separable), and would have a more natural home in a pragma like
Design::BestPractice (or Lingua::Franca or Wheels::Training or
Lingua::Fascist, depending on one's point of view).  Maybe I'm just thinking
too neutrally of unless === if not, rather than unless === if shouldn't be.

Either way, it's a pretty minor point -- certainly nothing as mind-bending
as a good JAPH or with the scary security implications of
parens-specify-an-executable-block, so 'nuff said.

--
Regards,
Charles Bailey
Lists: bailey _dot_ charles _at_ gmail _dot_ com
Other: bailey _at_ newman _dot_ upenn _dot_ edu


[svn:perl6-synopsis] r14384 - doc/trunk/design/syn

2007-04-26 Thread larry
Author: larry
Date: Thu Apr 26 18:47:39 2007
New Revision: 14384

Modified:
   doc/trunk/design/syn/S03.pod

Log:
Clarification of empty range semantics requested by coke++


Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod(original)
+++ doc/trunk/design/syn/S03.podThu Apr 26 18:47:39 2007
@@ -12,9 +12,9 @@
 
   Maintainer: Larry Wall <[EMAIL PROTECTED]>
   Date: 8 Mar 2004
-  Last Modified: 13 Apr 2007
+  Last Modified: 26 Apr 2007
   Number: 3
-  Version: 113
+  Version: 114
 
 =head1 Overview
 
@@ -2148,6 +2148,9 @@
 
 @[EMAIL PROTECTED], @array[-1] xx *
 
+An empty Range cannot be iterated; it returns a C instead.  An empty
+range still has a defined min and max, but the min is greater than the max.
+
 =item *
 
 The unary C<^> operator generates a range from C<0> up to