Re: [perl #128984] Feature request (wontfix?): perl -c executes BEGIN and CHECK blocks

On Thu, Aug 18, 2016 at 6:18 PM, Claudio wrote: > Taking Brandon's answer in considiration, does this mean that no perl6 > code could be parsed as correct without (implicit) BEGIN blocks or that it > will only work in -let's say- 99% of the time (file without a begin block)? I did say "while th

Re: [perl #128984] Feature request (wontfix?): perl -c executes BEGIN and CHECK blocks

On Thu, Aug 18, 2016 at 6:21 PM, Patrick R. Michaud via RT < perl6-bugs-follo...@perl.org> wrote: > On Thu, Aug 18, 2016 at 10:38:57AM -0400, Brandon Allbery wrote: > > On Thu, Aug 18, 2016 at 9:13 AM, Claudio > > wrote: > > > > > Tools like vim-syntastic and atom use 'perl6-c' (the only valid li

[perl #128986] [NYI] Forbid \b (backspace) escape sequence in regexes to catch a P5-ism

# New Ticket Created by Sam S. # Please include the string: [perl #128986] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128986 > S05 says: Backslash escapes for literal chara

Re: [perl #128985] [SEGV] in multi-level list reduction/evaluation

pyanfar Z$ rakudobrew exec perl6-valgrind-m -e 'say ^1000 .grep: -> $n {([+] ^$n .grep: -> $m {$m and $n %% $m}) == $n } # Perfect numbers?' This is Rakudo Perl 6 running in valgrind, a tool for debuggi

[perl #128985] [SEGV] in multi-level list reduction/evaluation

# New Ticket Created by Aaron Sherman # Please include the string: [perl #128985] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128985 > Was trying to list perfect numbers: [12:37] m: say ^1000 .grep: -> $n {([+] ^$n .grep:

Re: [perl #128984] Feature request (wontfix?): perl -c executes BEGIN and CHECK blocks

On Thu, Aug 18, 2016 at 10:38:57AM -0400, Brandon Allbery wrote: > On Thu, Aug 18, 2016 at 9:13 AM, Claudio > wrote: > > > Tools like vim-syntastic and atom use 'perl6-c' (the only valid linter for > > now) to report syntax errors. Because "perl6 -c" executes code (BEGIN and > > CHECK blocks as d

Re: [perl #128969] AutoReply: [RFC] Proposal to move grammar related part of error messages behind a runtime flag

Another suggestion would be to leave them as is unless you're running with '-e' (though again with an option to turn them on in that case if you so desire). On Tue, Aug 16, 2016 at 9:25 PM, perl6 via RT wrote: > Greetings, > > This message has been automatically generated in response to the > cr

Re: [perl #128984] Feature request (wontfix?): perl -c executes BEGIN and CHECK blocks

On Thu, Aug 18, 2016 at 9:13 AM, Claudio wrote: > Tools like vim-syntastic and atom use 'perl6-c' (the only valid linter for > now) to report syntax errors. Because "perl6 -c" executes code (BEGIN and > CHECK blocks as documented), this is a security concern for external code. The problem is th

[perl #128984] Feature request (wontfix?): perl -c executes BEGIN and CHECK blocks

# New Ticket Created by Claudio # Please include the string: [perl #128984] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128984 > Hi, This is more of a post-it note than a real feature request, but here it goes (related wi

[perl #128983] Feature request: output errors as JSON

# New Ticket Created by Claudio # Please include the string: [perl #128983] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128983 > Hi, I having a go at adding syntax checking support to vim using the syntastic plugin (https