Re: Quoting issue in Windows

On 2019-12-03 19:14, Paul Procacci wrote: echo isn't a great example at all.  echo is both OS and SHELL specific. Not only that, echo has argv to work with; each with it's own terminating '\0'. It absolutely can be quite literal, though that doesn't stop the implementors from doing whatever the

Re: Quoting issue in Windows

echo isn't a great example at all. echo is both OS and SHELL specific. Not only that, echo has argv to work with; each with it's own terminating '\0'. It absolutely can be quite literal, though that doesn't stop the implementors from doing whatever they want. Here's a snippet from my own OS's `ma

Re: Quoting issue in Windows

My keeper file on the subject; perl6: literal quotes: Reference(s): https://docs.perl6.org/language/quoting Everything inside single quotes ("''") is literal, EXCEPT if a backslash (escape) is involved. In that case use Q or a double backslash (escape the escape) $ p6 'say "Drive B:

Re: Quoting issue in Windows

On 2019-12-03 17:31, Paul Procacci wrote: When a string is specified in single quotes, perl6 (or any other language that I'm aware of) will not evaluate or interpret an escape character EXCEPT when the escape is follow'd by a single quote (') or backslash(\). These HAVE to be escaped and the i

Re: Quoting issue in Windows

On 2019-12-03 08:04, yary wrote: >Seems to me there is a bug here that > >     rakudo-star-2019.03-x86_64 (JIT).msi > >is trying to interpret things inside single quotes. If you can post a file that does that, I'll eat my hat! here's a little recap of the basic quoting, which does exact

Re: rmdir question

On 03/12/2019 04:46, Paul Procacci wrote: > On success it return a Bool::True. > On failure it throws an exception. > It doesn't crash the program. > If you are interested in handling the exception, add logic to handle it. > > Examples: > --- > # mkdir a ; `which perl6` -e "

Re: Quoting issue in Windows

>Seems to me there is a bug here that > > rakudo-star-2019.03-x86_64 (JIT).msi > >is trying to interpret things inside single quotes. If you can post a file that does that, I'll eat my hat! here's a little recap of the basic quoting, which does exactly the same in recent perl6 and decade-plus

Re: I need array of hashes help

On 2019-12-03 03:17, Fernando Santagata wrote: You can't write "my @y[0]". -- Fernando Santagata Hi Fernando, You called it. I had to declare @y first before assigning hashes to it. Thank you! -T $ p6 'my @y[0]={a=>"aa",b=>"bb"};' Illegal dimension in shape: 0. All dimensions must

Re: I need array of hashes help

Try: p6 'my @y; @y[0]={a=>"aa",b=>"bb"}; push @y, {a=>"AA",b=>"BB"}; for @y.kv -> $I, $J { say "Index $I $J $J" }; say "elements " ~ @y.elems;' You can't write "my @y[0]". On Tue, Dec 3, 2019 at 11:53 AM ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2019-12-03 02:39, ToddAn

Re: I need array of hashes help

On 2019-12-03 02:39, ToddAndMargo via perl6-users wrote: Hi All, What am I doing wrong here? $ p6 'my @y; my %x=(a=>"aa", b=>"bb"); @y[0] = %x; %x="AA"; %x="BB"; push @y,{%x}; for @y.kv -> $I, $J { say "Index $I  $J $J" }; say "elements " ~ @y.elems;' Index 0  AA  BB Index 1  AA  BB element

Re: Quoting issue in Windows

On Tue, Dec 3, 2019 at 3:55 AM ToddAndMargo via perl6-users mailto:perl6-users@perl.org>> wrote: On 2019-12-02 07:02, The Sidhekin wrote: > > On Mon, Dec 2, 2019 at 11:07 AM ToddAndMargo via perl6-users > mailto:perl6-users@perl.org>

I need array of hashes help

Hi All, What am I doing wrong here? $ p6 'my @y; my %x=(a=>"aa", b=>"bb"); @y[0] = %x; %x="AA"; %x="BB"; push @y,{%x}; for @y.kv -> $I, $J { say "Index $I $J $J" }; say "elements " ~ @y.elems;' Index 0 AA BB Index 1 AA BB elements 2 It should be Index 0 aa bb Index 1 AA BB elemen

Re: Quoting issue in Windows

i'm on linux and single quotes behave like they're supposed to, and only escape a single quote with a backslash. Are you sure the issue you're having isn't with the command line or something? On Tue, Dec 3, 2019 at 3:55 AM ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2019-12-0