Re: I need a second pair of eyes

On 2020-05-27 14:26, Will Coleda wrote: Part of framing the question in the first place is reducing the problem code to as small a subset as possible that still exhibits the problem. AND THEY ALWAYS WORK! ! No reporting that back to the developers. Often, in the course of doi

Re: I need a second pair of eyes

Part of framing the question in the first place is reducing the problem code to as small a subset as possible that still exhibits the problem. Often, in the course of doing this "golfing", you'll uncover the problem yourself. On Wed, May 27, 2020 at 4:59 PM ToddAndMargo via perl6-users wrote: >

Re: I need a second pair of eyes

On 2020-05-27 13:38, Veesh Goldman wrote: well, like I said before, if you just show ALL of your code, then we'd be able to know what happened. I fixed the mistake I made, which also fixed the wrong output from "say", so all is working now and I doubt the issue would reproduce. The code itself

Re: I need a second pair of eyes

well, like I said before, if you just show ALL of your code, then we'd be able to know what happened. On Wed, May 27, 2020 at 8:55 PM ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 2020-05-27 07:27, Brad Gilbert wrote: > > The point was that ｢say｣ will print undefined values wit

Re: I need a second pair of eyes

On 2020-05-27 07:27, Brad Gilbert wrote: The point was that ｢say｣ will print undefined values without complaining. Really debug statements should be more like: $*STDERR.put: ｢%CommandLine = ｣, %CommandLine; Or more succinctly: dd %CommandLine; Which does bring to the forefront, wh

Re: I need a second pair of eyes

the names? If so, is there a way you could create a minimal example, a short program that, when run on your system, always behaves this way, and post it (attach the source file, don't retype it) in full, so that people can try to run it on their systems and see if "say" really does s

Re: I need a second pair of eyes

The point was that ｢say｣ will print undefined values without complaining. Really debug statements should be more like: $*STDERR.put: ｢%CommandLine = ｣, %CommandLine; Or more succinctly: dd %CommandLine; On Wed, May 27, 2020 at 1:39 AM Peter Pentchev wrote: > On Tue, May 26, 2020 at 0

Re: I need a second pair of eyes

On Tue, May 26, 2020 at 07:16:54PM -0700, ToddAndMargo via perl6-users wrote: > On 2020-05-25 23:42, ToddAndMargo via perl6-users wrote: > > HI All, > > > > I am missing something here: > > > > > > 154:   # figure out the label > > 155:   say %CommandLine; > > 156:   if "%CommandLine".starts-wit

Re: I need a second pair of eyes

On 2020-05-26 19:16, ToddAndMargo via perl6-users wrote: On 2020-05-25 23:42, ToddAndMargo via perl6-users wrote: HI All, I am missing something here: 154:   # figure out the label 155:   say %CommandLine; 156:   if "%CommandLine".starts-with( "[" )  && 157:  "%CommandLine".contains( "]"

Re: I need a second pair of eyes

On 2020-05-25 23:42, ToddAndMargo via perl6-users wrote: HI All, I am missing something here: 154:   # figure out the label 155:   say %CommandLine; 156:   if "%CommandLine".starts-with( "[" )  && 157:  "%CommandLine".contains( "]" ) { BACKUP:\MyDocsBackup\backup1 Cannot resolve caller i

Re: I need a second pair of eyes

On Tue, May 26, 2020 at 4:54 PM yary > wrote: From this much 158: Cannot resolve caller index(Str:U: Str:D); none of these signatures match: "index" is being called with the 1st arg undefined, 2nd arg defined. There is no "index" multi handling the

Re: I need a second pair of eyes

This is more of how I would structure it with %CommandLine { .say; # if /^ '[' .*? ']' / { if .starts-with('[') && .contains(']') { ... } } else { say 'no backup path given' } We can skip checking ｢.starts-with｣ and ｢.contains｣ if th

Re: I need a second pair of eyes

>From this much 158: Cannot resolve caller index(Str:U: Str:D); none of these signatures match: "index" is being called with the 1st arg undefined, 2nd arg defined. There is no "index" multi handling the 1st undefined arg, is my guess. -y On Tue, May 26, 2020 at 4:41 AM ToddAndMargo via perl6-

Re: I need a second pair of eyes

On 2020-05-26 01:40, ToddAndMargo via perl6-users wrote: On 2020-05-26 01:37, ToddAndMargo via perl6-users wrote: 155: A:\YourDocs\backup1 156: No   157: No     158: Cannot reso

Re: I need a second pair of eyes

On 2020-05-26 01:37, ToddAndMargo via perl6-users wrote: 155: A:\YourDocs\backup1     156: No  157: No    158: Cannot resolve caller index(Str:U: Str:D); none of these signatures

Re: I need a second pair of eyes

This is Rakudo version 2020.05.1 built on MoarVM version 2020.05 implementing Raku 6.d. It is back at it again. The second test, I sent it something with brackets in it. It is the failed test to goes wonkers I put some debugging and is seems that it does not like my `&&` 155: say %CommandLi

Re: I need a second pair of eyes

> On Tue, May 26, 2020, 09:45 ToddAndMargo via perl6-users > mailto:perl6-users@perl.org>> wrote: > > HI All, > > I am missing something here: > > > 154: # figure out the label > 155: say %CommandLine; > 156: if "%CommandLine".starts-with( "["

I need a second pair of eyes

HI All, I am missing something here: 154: # figure out the label 155: say %CommandLine; 156: if "%CommandLine".starts-with( "[" ) && 157: "%CommandLine".contains( "]" ) { BACKUP:\MyDocsBackup\backup1 Cannot resolve caller index(Str:U: Str:D); none of these signatures match: (L

Re: Need a second pair of eyes

This explanation confuses me a bit, actually. (more inline) On Tue, Sep 26, 2017 at 9:45 AM, Larry Wall wrote: > In slightly greater detail, we're currently treating an undeclared > variable as a syntax error rather than a semantic error, and we treat > those differently. Syntax errors are usua

Re: Need a second pair of eyes

On Mon, Sep 25, 2017 at 10:25:42AM -0400, Brandon Allbery wrote: : So as to make this not entirely content-free: I would suggest that the : string language note the line on which it sees a bare newline, and if it : subsequently hits a syntax error while still parsing that string it could : output s

undeclared variables inside double-quoted string lwas: Re: Need a second pair of eyes]

On 26/09/17 04:26, Brandon Allbery wrote: > On Mon, Sep 25, 2017 at 10:23 PM, ToddAndMargo > wrote: > > On 09/25/2017 07:25 AM, Brandon Allbery wrote: > > So as to make this not entirely content-free: I would suggest > that the string language note

Re: Need a second pair of eyes

On Mon, Sep 25, 2017 at 10:49 PM, ToddAndMargo wrote: > There is another operating system other than Linux? I > had heard rumors of that: it is slow, expensive, crashes > all the time. But I thought is was only a story to frighten > little children and young programmers. SAY IT ISN'T > TRUE!!

Re: Need a second pair of eyes

O> On Mon, Sep 25, 2017 at 10:19 AM, Brandon Allbery > wrote: On Mon, Sep 25, 2017 at 3:09 AM, Julien Simonet mailto:kernel.jul...@gmail.com>> wrote: I think your problem is coming from a (") missing at line 3. At the same line, the semicolon

Re: Need a second pair of eyes

On 09/25/2017 06:39 AM, Timo Paulssen wrote: Second itteration: #!/usr/bin/env perl6 say "Full file name <$?FILE>"; my $IAm; my $IAmFrom; $?FILE ~~ m|(.*\/)(.*)|; $IAmFrom = $0; $IAm = $1; say "IAm    <$IAm>"; say "IAmFrom    <$IAmFrom>"; Please don't use string function

Re: Need a second pair of eyes

On 09/25/2017 12:51 PM, Parrot Raiser wrote: ToddAndMargo might save some time by asking "Is this a problem someone else might have solved, and if so, how?" before plunging ahead and coding. From this and previous postings, it looks as though the answer might frequently start with "Yes", and woul

Re: Need a second pair of eyes

On Mon, Sep 25, 2017 at 10:23 PM, ToddAndMargo wrote: > On 09/25/2017 07:25 AM, Brandon Allbery wrote: > >> So as to make this not entirely content-free: I would suggest that the >> string language note the line on which it sees a bare newline, and if it >> subsequently hits a syntax error while

Re: Need a second pair of eyes

On 09/25/2017 07:25 AM, Brandon Allbery wrote: So as to make this not entirely content-free: I would suggest that the string language note the line on which it sees a bare newline, and if it subsequently hits a syntax error while still parsing that string it could output something like perl 5's

Re: Need a second pair of eyes

ToddAndMargo might save some time by asking "Is this a problem someone else might have solved, and if so, how?" before plunging ahead and coding. From this and previous postings, it looks as though the answer might frequently start with "Yes", and would save a lot of redundant effort.

Re: Need a second pair of eyes

So as to make this not entirely content-free: I would suggest that the string language note the line on which it sees a bare newline, and if it subsequently hits a syntax error while still parsing that string it could output something like perl 5's "Possible runaway multi-line string starting on li

Re: Need a second pair of eyes

On Mon, Sep 25, 2017 at 3:09 AM, Julien Simonet wrote: > I think your problem is coming from a (") missing at line 3. > At the same line, the semicolon (;) is misplaced : it should be at the end > if line. > It took older perl over a decade to come up with better error messages for this. Can we

Re: Need a second pair of eyes

> Second itteration: > > > #!/usr/bin/env perl6 > > say "Full file name <$?FILE>"; > > my $IAm; > my $IAmFrom; > > $?FILE ~~ m|(.*\/)(.*)|; > $IAmFrom = $0; > $IAm = $1; > say "IAm    <$IAm>"; > say "IAmFrom    <$IAmFrom>"; > Please don't use string functions on paths; doing it

Re: Need a second pair of eyes

On 09/25/2017 12:22 AM, ToddAndMargo wrote: On 09/25/2017 12:14 AM, ToddAndMargo wrote: Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo a écrit : 1: #!/usr/bin/env perl6 2: 3: say "Full file name <$?FILE;> 4: 5: my $IAmFrom; 6: $IAmFrom = $?FILE; 7:

Re: Need a second pair of eyes

On 09/25/2017 12:14 AM, ToddAndMargo wrote: Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo a écrit : 1: #!/usr/bin/env perl6 2: 3: say "Full file name <$?FILE;> 4: 5: my $IAmFrom; 6: $IAmFrom = $?FILE; 7: $IAmFrom ~~ \.*/||; 8: say "IAmFrom <$IAm

Re: Need a second pair of eyes

Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo a écrit : 1: #!/usr/bin/env perl6 2: 3: say "Full file name <$?FILE;> 4: 5: my $IAmFrom; 6: $IAmFrom = $?FILE; 7: $IAmFrom ~~ \.*/||; 8: say "IAmFrom <$IAmFrom>"; $ /home/linuxutil/FileTest.

Re: Need a second pair of eyes

Hello, I think your problem is coming from a (") missing at line 3. At the same line, the semicolon (;) is misplaced : it should be at the end if line. I hope I helped :) Le 25 septembre 2017 08:55:59 GMT+02:00, ToddAndMargo a écrit : > >1: #!/usr/bin/env perl6 >2: >3: say "Full file name

Need a second pair of eyes

1: #!/usr/bin/env perl6 2: 3: say "Full file name <$?FILE;> 4: 5: my $IAmFrom; 6: $IAmFrom = $?FILE; 7: $IAmFrom ~~ \.*/||; 8: say "IAmFrom <$IAmFrom>"; $ /home/linuxutil/FileTest.pl6 ===SORRY!=== Error while compiling /home/linuxutil/FileTest.pl6 Variable '$IAmFrom' is not declared at /hom