On Tue, Mar 15, 2005 at 11:14:07AM -0800, Larry Wall wrote:
> On Wed, Mar 16, 2005 at 02:57:36AM +0800, Autrijus Tang wrote:
> : So, between the two consistencies, do you think that the more DWIMmy
> : one of parsing "0o123" is more helpful? I'll implement it tomorrow
> : if that's the case. :)
>
I'm unsure how chomp() should work with p6; it's not listed
in S29 yet.
Should the semantics of g.p6 below be the same for p5 and p6?
It produces different output when run with p5 compared to pugs,
at least that's my sleepy brain sees.
# cat g.p6
my @x = ( "a\n", "1", "x\n" );
for (@x) { print "1
I am very happy to announce Pugs 6.0.12, with full support for
source code written in UTF-8, and Perl5-compatible regular
expression matching as rx:perl5//.
With this release out, I will divert some of my time on the
Compiler backend. See http://use.perl.org/~autrijus/journal/23757
and tomorrow's
Andrew Savige wrote:
I'm unsure how chomp() should work with p6; it's not listed
in S29 yet.
It'll be a lot like it is in Perl5, in that it'll remove any trailing
newlineish looking characters, and returns the number of characters that
I can't answer completely until we finish discussing on p6l h
Larry Wall wrote:
On Sat, Mar 19, 2005 at 11:03:40PM +1100, Andrew Savige wrote:
: 2) Documentation.
:Where is the slurp built-in documented? I couldn't find it
:in any of the Synopses (including Rod Adams' recent S29).
:In desperation, I googled and found CPAN Perl6::Slurp.
The officia
Here are my shortest-term plans that affect Pugs:
1. Circa March 21-23, I will release the Perl 5 version of
SQL::Routine v0.57 to CPAN, plus updated Perl 5 versions of its
dependents, and then announce their availability to dbi-users and
other such forums as "developer release #2". This will c
