Thank you for the clarification. That means that at the moment, most files
(i.e. the ones written in OO) will have a have errors without a BEGIN block
(i.e. the use of self).
As 'perl6 -c' being for now the *only* way to check the syntax of a code
file, the security concerns should not be easily d
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
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
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
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
# 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
