Re: Need a second pair of eyes

2017-09-26 Thread Brandon Allbery
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

2017-09-26 Thread Larry Wall
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]

2017-09-26 Thread Timo Paulssen
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

2017-09-25 Thread Brandon Allbery
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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread Brandon Allbery
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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread Parrot Raiser
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

2017-09-25 Thread Brandon Allbery
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

2017-09-25 Thread Brandon Allbery
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

2017-09-25 Thread Timo Paulssen
> 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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread ToddAndMargo
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

2017-09-25 Thread Julien Simonet
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