For example: "use parrot Foo::Bar", which would load parrot library under
Foo/Bar. However, this would be easy and useful for rakudo, but would not for
other possible Perl6 implementations.
_
Hot
Author: lwall
Date: 2010-06-24 22:54:50 +0200 (Thu, 24 Jun 2010)
New Revision: 31442
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
[S03] qualify misleading assertion re 1,2,3...$n when $n < 3
Modified: docs/Perl6/Spec/S03-operators.pod
==
yary wrote:
Reminds me of an article of yore from The Perl Journal "Localizing
Your Perl Programs" http://interglacial.com/tpj/13/ which discusses
the reasoning behind Locale::Maketext
the point of which is that the "values" you're looking up should be
able to be functions, to handle some edge c
Reminds me of an article of yore from The Perl Journal "Localizing
Your Perl Programs" http://interglacial.com/tpj/13/ which discusses
the reasoning behind Locale::Maketext
the point of which is that the "values" you're looking up should be
able to be functions, to handle some edge cases where not
Moritz Lenz wrote:
However there are things that can be translated to other languages, and
that is documentation, error messages and warnings.
And the next step is non-error messages intended to be seen by users.
The latter two require that we standardize exception types and messages,
and pro
yary wrote:
Yes but- the OP wasn't asking about
my Str $s;
my Int $i=$s;
not failing at compile time, the question was about
my Int $i='abc';
or how about
sub square(Int $n='o hai');
Would it be wrong for the "cut-off point" be after an immediate assignment/
declaration of a built-in type to
On Thu, Jun 24, 2010 at 12:08 AM, Jan Ingvoldstad wrote:
> On Wed, Jun 23, 2010 at 20:21, Darren Duncan >wrote:
>
> > If all invocations of myop use a code literal for the $y argument, then
> > this can be checked at compile time, but if the argument is a variable,
> they
> > have to look further
Am 23.06.2010 22:51, schrieb Aaron Sherman:
Moving on to more general theories on the matter, I believe that localized
dialects of programming languages are always a bad idea.
I totally agree.
However there are things that can be translated to other languages, and
that is documentation, error
# New Ticket Created by Lewis Wall
# Please include the string: [perl #76038]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=76038 >
$ perl6 -e 'class A {our $.x = 4}; say A.new.x'
Method 'x' not found for invocant of class
# New Ticket Created by Tadeusz Sośnierz
# Please include the string: [perl #76022]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=76022 >
Rakudo does not complain about required parameters put after these
with default valu
# New Ticket Created by Paweł Pabian
# Please include the string: [perl #75990]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=75990 >
It makes listing all object instance methods impossible:
[16:21] rakudo: Seq.new.^meth
On Wed, Jun 23, 2010 at 20:21, Darren Duncan wrote:
> If all invocations of myop use a code literal for the $y argument, then
> this can be checked at compile time, but if the argument is a variable, they
> have to look further out.
>
>
Yup.
For those who don't quite see what this leads to, consi
12 matches
Mail list logo
