It also seems to me that 'scalar' gives the wrong impression compared to
arrays. A scalar in a vector is a component of a vector.
I was thinking of "generic".
Hence "$variable" is a generic variable because it can hold any type of
content.
On Friday, June 09, 2017 02:10 PM, Gabor Szabo wrot
Looking at https://docs.perl6.org/language/variables there are 4
variable types with sigil: $, @, %, &.
In Perl 5 I used to call them scalar, array, hash, and function
respectively, even if the scalar variable had a reference to an array
in it.
How do you call them in Perl 6?
As I understand @ a
On Thu, 08 Jun 2017 16:39:40 -0700, ju...@tnx.nl wrote:
> Because putting bundled libraries in ./lib or ../lib relative to the
> executable is so common, I'd like to request a feature for shortcuts for
> these.
>
> I'm thinking of:
>
> use lib :parentdir;
> # as a shortcut for:
> use
On Thu, 08 Jun 2017 16:39:40 -0700, ju...@tnx.nl wrote:
> Because putting bundled libraries in ./lib or ../lib relative to the
> executable is so common, I'd like to request a feature for shortcuts for
> these.
>
> I'm thinking of:
>
> use lib :parentdir;
> # as a shortcut for:
> use
On Thu, 08 Jun 2017 16:33:33 -0700, ju...@tnx.nl wrote:
> It'd be nice if I didn't have to stringify this myself:
>
> use lib $*PROGRAM.resolve.sibling('lib');
>
> Currently, this results in the following failure:
>
> Type check failed in binding to parameter '$spec'; expected Str but
>
On Thu, 08 Jun 2017 16:33:33 -0700, ju...@tnx.nl wrote:
> It'd be nice if I didn't have to stringify this myself:
>
> use lib $*PROGRAM.resolve.sibling('lib');
>
> Currently, this results in the following failure:
>
> Type check failed in binding to parameter '$spec'; expected Str but
>
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131542]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131542 >
the `state $l` appears to break the moment we add an unrelated named param to
it (doesn't
> Result:
> Malformed UTF-8 at line 1 col 1029
> in block at ./test.pl:2
This is slightly different to what is in documentation.
' "[TBD]" are to be defined later' is in the file
I took "defined" to mean "done" rather than "documented". In other
words, something that did not exist, but should exist.
What seems to be the case is that "defined" means "exists, but is
This is slightly different to what is in documentation.
' "[TBD]" are to be defined later' is in the file
I took "defined" to mean "done" rather than "documented". In other
words, something that did not exist, but should exist.
What seems to be the case is that "defined" means "exists, but is n
On Wed, 07 Jun 2017 11:46:03 -0700, ben-goldb...@hotmail.com wrote:
> On Monday, June 05, 2017 5:05 PM, Will Coleda via RT wrote:
> > On Fri, 02 Jun 2017 23:29:40 -0700, ben-goldb...@hotmail.com wrote:
> > > On #perl6 IRC, I typed this:
> > >
> > > m: my \foo = Callable but role :: { };
> > > <+c
On Wed, 07 Jun 2017 11:46:03 -0700, ben-goldb...@hotmail.com wrote:
> On Monday, June 05, 2017 5:05 PM, Will Coleda via RT wrote:
> > On Fri, 02 Jun 2017 23:29:40 -0700, ben-goldb...@hotmail.com wrote:
> > > On #perl6 IRC, I typed this:
> > >
> > > m: my \foo = Callable but role :: { };
> > > <+c
# New Ticket Created by Juerd Waalboer
# Please include the string: [perl #131541]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131541 >
Because putting bundled libraries in ./lib or ../lib relative to the
executable is so c
TBD there indicates that the documentation is yet to be done.
On Thu, Jun 8, 2017 at 4:38 AM, Richard Hainsworth
wrote:
> Thanks for feedback. A follow up:
>
>
>>
>> Yes, use `no precompilation` pragma.
>>
>>
> So I would have in the topmost program:
>
> use v6.c;
> no precompilation;
>
> In the
TBD there indicates that the documentation is yet to be done.
On Thu, Jun 8, 2017 at 4:38 AM, Richard Hainsworth
wrote:
> Thanks for feedback. A follow up:
>
>
>>
>> Yes, use `no precompilation` pragma.
>>
>>
> So I would have in the topmost program:
>
> use v6.c;
> no precompilation;
>
> In the
# New Ticket Created by Juerd Waalboer
# Please include the string: [perl #131540]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131540 >
It'd be nice if I didn't have to stringify this myself:
use lib $*PROGRAM.resolve.
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131539]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131539 >
Last night, I fixed a bug and used RakudoPrereq.pm6 to lock my module to latest
and great
I think this is just another example of the compile time closures problem
since EXPORT runs at compile time in during the loading module's
compilation.
https://rt.perl.org/Public/Bug/Display.html?id=128636
For an example in my own code:
https://github.com/spitsh/spitsh/blob/master/lib/Spit/Const
I think this is just another example of the compile time closures problem
since EXPORT runs at compile time in during the loading module's
compilation.
https://rt.perl.org/Public/Bug/Display.html?id=128636
For an example in my own code:
https://github.com/spitsh/spitsh/blob/master/lib/Spit/Const
On Thu, Jun 8, 2017 at 6:22 AM, Zoffix Znet via RT <
perl6-bugs-follo...@perl.org> wrote:
>
> m: sub infix:<2> { $^a + $^b }; say 2 2 2
> rakudo-moar 1ac799: OUTPUT: «4»
>
> Because when an op is expected. There's just one op named `2`. And when
> a term is expected, there's just one term
After a conversation in #perl6-dev[^1], I'm rejecting this ticket.
Unlike invisible operators (RT#128159), there's no security risk involved.
Unlike `&0` (RT#128159), there's no ambiguity in what the non-throwing
behaviour is supposed to be.
This is just a peculiar intersection of two very-well d
After a conversation in #perl6-dev[^1], I'm rejecting this ticket.
Unlike invisible operators (RT#128159), there's no security risk involved.
Unlike `&0` (RT#128159), there's no ambiguity in what the non-throwing
behaviour is supposed to be.
This is just a peculiar intersection of two very-well d
I do understand the operand-operator idea now, but I think that allowing
the same symbol to be both operand and operator is a terrible idea.
Feel free to disagree, I'm not going to argue that point.
Otherwise:
And since nobody is going to use that > > Yes! Exactly. You've put the nail in
your
Quoting Joachim Durchholz :
> Am 08.06.2017 um 01:11 schrieb Zoffix Znet via RT:
>> Quoting Joachim Durchholz :
> That cannot be correct. There's that other rule that turns
> superscripts into exponents.
Except it IS correct. There's no "other rule". There are No characters as
literals
and supe
Quoting Joachim Durchholz :
> Am 08.06.2017 um 01:11 schrieb Zoffix Znet via RT:
>> Quoting Joachim Durchholz :
> That cannot be correct. There's that other rule that turns
> superscripts into exponents.
Except it IS correct. There's no "other rule". There are No characters as
literals
and supe
Thanks for feedback. A follow up:
> Yes, use `no precompilation` pragma.
>
>
So I would have in the topmost program:
use v6.c;
no precompilation;
In the documentation (https://docs.perl6.org/language/pragmas),
precompilation is labelled [TBD]
So is it ignored ?
Regards,
Richard
Thanks for feedback. A follow up:
Yes, use `no precompilation` pragma.
So I would have in the topmost program:
use v6.c;
no precompilation;
In the documentation (https://docs.perl6.org/language/pragmas),
precompilation is labelled [TBD]
So is it ignored ?
Regards,
Richard
27 matches
Mail list logo
