I don’t think we have a separate queue for REPL, so
https://github.com/rakudo/rakudo/issues is the place
> On 16 Sep 2018, at 15:01, Fernando Santagata
> wrote:
>
> Should I report this here: https://github.com/rakudo/rakudo/ or there's a
> specific location for the REPL?
>
> On Sun, Sep 16,
Should I report this here: https://github.com/rakudo/rakudo/ or there's a
specific location for the REPL?
On Sun, Sep 16, 2018 at 2:28 PM Elizabeth Mattijsen wrote:
> Definitely a bug. Which seems to be limited to the REPL only, fortunately.
>
> > On 16 Sep 2018, at 12:57, Fernando Santagata
>
Definitely a bug. Which seems to be limited to the REPL only, fortunately.
> On 16 Sep 2018, at 12:57, Fernando Santagata
> wrote:
>
> Hello,
>
> I found this behavior quite strange:
>
>> my int32 $a = 2
> 2
>> $a.^name
> Int
>> $a.WHAT
> At Frame 1, Instruction 20, op 'getlex_ni', operand 0
Thank you. Silly me, thinking "this is so simple I don't need to run it
through the command-line to test it." :-)
Anway, yeah,
say $_ for reverse lines
Aaron Sherman, M.:
P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com
Toolsmith, developer, gamer and life-long student.
It may make it clearer if I explain the broader objective. I'm trying
to learn P6 thoroughly by developing training courses to teach it from
scratch. (Fans of Gerald Weinberg may recognise the idea.) Obviously,
while doing so, I want to explore pathological cases, both to clarify
the concepts and t
On 19/09/16 16:02, Aaron Sherman wrote:
> I'm guessing that what you meant was "say as a function was what I > meant to
> use there." In which case: > > say for reverse lines > > or
> > for reverse lines { say } > > These are both valid ways of asking
for each element of the iterable > thing retur
I'm guessing that what you meant was "say as a function was what I meant to
use there." In which case:
say for reverse lines
or
for reverse lines { say }
These are both valid ways of asking for each element of the iterable thing
returned from lines to be printed with a newline.
But remember th
On Sun, Sep 18, 2016 at 16:49 Parrot Raiser <1parr...@gmail.com> wrote:
say { $_ } was the correct thing to use there. (I'm trying to avoid
> any mention of O-O for the moment.)
>
“Trying to avoid any mention of O-O” seems like a Perl 6 obfuscation or
golf constraint, not a desirable development o
On Sun, Sep 18, 2016 at 4:49 PM, Parrot Raiser <1parr...@gmail.com> wrote:
> What is this -> ;; $_? is raw { #`(Block|170303864) … } output?
It's the gist of a Block, which is what you asked for when you did a `say`
on an executable block.
Why do you believe `say { $_ }` is the right thing ther
It is the .perl representation of a Block.
> On 18 Sep 2016, at 22:49, Parrot Raiser <1parr...@gmail.com> wrote:
>
> say { $_ } was the correct thing to use there. (I'm trying to avoid
> any mention of O-O for the moment.)
> say {} was a "what happens if I do this" exercise.
>
> What is this ->
say { $_ } was the correct thing to use there. (I'm trying to avoid
any mention of O-O for the moment.)
say {} was a "what happens if I do this" exercise.
What is this -> ;; $_? is raw { #`(Block|170303864) … } output?
On 9/18/16, Brent Laabs wrote:
> Remember you can call a block with parenthe
Remember you can call a block with parentheses:
> say { 11 + 31 };
-> ;; $_? is raw { #`(Block|140268472711224) ... }
> say { 11 + 31 }();
42
On Sun, Sep 18, 2016 at 12:58 PM, Elizabeth Mattijsen
wrote:
> I think you want:
>
> .say for reverse lines;
>
> not sure what you are trying to achie
I think you want:
.say for reverse lines;
not sure what you are trying to achieve otherwise, but:
say { }
producing something like
-> ;; $_? is raw { #`(Block|170303864) … }
feels entirely correct to me. :-)
Liz
> On 18 Sep 2016, at 21:52, Parrot Raiser <1parr...@gmail.com> wrote
13 matches
Mail list logo
