On Tue, Feb 3, 2009 at 8:34 AM, Richard Hainsworth wrote:
> I strongly believe the current S16 needs rewriting from scratch. This
> approach seems far more more perl6-ish. I tried to draft a new S16, but
> realised I simply dont have the knowledge (or the time to acquire the
> knowledge) necessary
Leon (>):
> It seems S03 and S16 disagree on the meaning of $filename ~~ :e
> though. According to S16 it means $filename.:e, according to S03 it
> means $filename.e. I think it was discussed some time ago and S16 is
> correct.
No, $filename.e is the newer one; S16 is out-of-date on that point.
/
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #63004]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=63004 >
Parrot r36318 (before the merge that broke Rakudo), and Rakudo 21f374.
For some reason,
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #63014]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=63014 >
I just got bitten by a logical bug of sorts: @array[0..0]
results in an element, not in
Author: ruoso
Date: 2009-02-04 16:37:16 +0100 (Wed, 04 Feb 2009)
New Revision: 25182
Modified:
docs/Perl6/Spec/S16-io.pod
Log:
[spec/S16] proposed role-based api
Modified: docs/Perl6/Spec/S16-io.pod
===
--- docs/Perl6/Spec/S16-io.
pugs-comm...@feather.perl6.nl writes:
> +=item method Int read($buf is rw, int $length)
I'm not sure that using a native int is the right thing here. If
whatever the implementation uses as int is narrower than size_t, that
forces the programmer to use an Int and do the necessary loop.
On the oth
Em Qua, 2009-02-04 às 16:45 +, Aaron Crane escreveu:
> pugs-comm...@feather.perl6.nl writes:
> > +=item method Int read($buf is rw, int $length)
> I'm not sure that using a native int is the right thing here. If
> whatever the implementation uses as int is narrower than size_t, that
> forces t
Daniel Ruoso writes:
> Em Qua, 2009-02-04 às 16:45 +, Aaron Crane escreveu:
> > pugs-comm...@feather.perl6.nl writes:
> > > +=item method Int read($buf is rw, int $length)
> > I'm not sure that using a native int is the right thing here. If
> > whatever the implementation uses as int is narrow
Author: ruoso
Date: 2009-02-04 18:45:46 +0100 (Wed, 04 Feb 2009)
New Revision: 25189
Modified:
docs/Perl6/Spec/S16-io.pod
Log:
[spec/S16] IO::Encoded role, including an idea I just had to allow
(IN|OUT)PUT_(RECORD|FIELD)_SEPARATOR semantics
Modified: docs/Perl6/Spec/S16-io.pod
===
On Wed, Feb 4, 2009 at 4:37 PM, wrote:
> +=head2 IO
> +
> +The base role only tags that this is an IO object for more generic
> +purposes. It doesn't specify any methods or attributes.
> +
Shouldn't IO::readable and IO::Writable do IO?
> +
> +=head2 IO::Closeable
> +
I still think this should
Leon Timmermans writes:
> On Wed, Feb 4, 2009 at 4:37 PM, wrote:
> > +=item method IO dup()
>
> Do we really want that?
If we label a thing as "POSIX", it should certainly make all the POSIX
functionality available, IMHO. I'd consider arguments that we should
pick different names for specific
In csh-influenced shells, you have access to the command history in a
way that lets you say "insert the third argument from the fourth
previous command here". In Lisp, you have the * variables with the
result of recent exppressions I think both of these capabilities are
very valuable in an intera
apparently this is a feature of Test.pm
though I think a very bad one
Gabor
On Wed, Feb 4, 2009 at 9:00 PM, perl6 via RT
wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
>"Test.pm eats the "Use of uninitiali
On Wed, Feb 04, 2009 at 01:52:17PM -0500, Mark J. Reed wrote:
> In csh-influenced shells, you have access to the command history in a
> way that lets you say "insert the third argument from the fourth
> previous command here". In Lisp, you have the * variables with the
> result of recent exppressi
Currently Test.pm disables the warnings to prevent tons of "Use of
uninitialized value" warnings when running the spectests.
Personally I think the spectests should not produce these warnings in
the first place, but I haven't found a good way to avoid/disable them yet.
Pm
Author: particle
Date: 2009-02-05 02:56:04 +0100 (Thu, 05 Feb 2009)
New Revision: 25198
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] adding --extract-from-text, -x; similar behavior to perl 5, but file may
now contain unicode text
Modified: docs/Perl6/Spec/S19-commandline.pod
Author: particle
Date: 2009-02-05 03:14:01 +0100 (Thu, 05 Feb 2009)
New Revision: 25200
Added:
t/spec/S19-command-line/
t/spec/S19-invalid/
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] --autoloop-split, -a: assigns result to @_; signature and option name
fixups
Modified: doc
wrote:
> -=item --autoloop-split, -F *expression*
> +=item --autoloop-delim, -F *expression*
>
> Pattern to split on (used with -a). Substitutes an expression for the
> default
> split function, which is C<{split ' '}>. Accepts unicode strings (as long as
Should the default pattern be ' ', o
Author: particle
Date: 2009-02-05 03:32:49 +0100 (Thu, 05 Feb 2009)
New Revision: 25201
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] shortened ++DEBUGGER to ++BUG, which seems a better mnemonic then ++DEB.
Modified: docs/Perl6/Spec/S19-commandline.pod
==
Author: particle
Date: 2009-02-05 03:42:30 +0100 (Thu, 05 Feb 2009)
New Revision: 25202
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] don't special-case C<-e6>, require C<-e '6;'>
Modified: docs/Perl6/Spec/S19-commandline.pod
=
Author: particle
Date: 2009-02-05 06:19:27 +0100 (Thu, 05 Feb 2009)
New Revision: 25205
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] remove -o, as -O now defaults to STDOUT -- TimToady++. shuffle some list
items around, to match order in perl6() signature
Modified: docs/Perl6/Spec
21 matches
Mail list logo
