Re: RFE: eval documentation

2018-06-14 Thread ToddAndMargo 

On 06/14/2018 02:52 PM, JJ Merelo wrote:



El jue., 14 jun. 2018 a las 23:34, ToddAndMargo (>) escribió:


On 06/14/2018 02:20 PM, JJ Merelo wrote:
 > Can you please open an issue in perl6/doc? It's the best to track
it,
 > and also to check that it's been solved to everyone's satisfaction.
 >
 > If you can't for any reason, I can open it for you, but I'll have to
 > keep coming back to see if it's OK when solved...

here?



https://github.com/perl6/doc



Right. Click on "issues", and just write :-)

--
JJ



https://github.com/perl6/doc/issues/2099

Re: RFE: eval documentation

2018-06-14 Thread JJ Merelo 
El jue., 14 jun. 2018 a las 23:34, ToddAndMargo ()
escribió:

> On 06/14/2018 02:20 PM, JJ Merelo wrote:
> > Can you please open an issue in perl6/doc? It's the best to track it,
> > and also to check that it's been solved to everyone's satisfaction.
> >
> > If you can't for any reason, I can open it for you, but I'll have to
> > keep coming back to see if it's OK when solved...
>
> here?
>
> 



> https://github.com/perl6/doc
>


Right. Click on "issues", and just write :-)

-- 
JJ

Re: RFE: eval documentation

2018-06-14 Thread ToddAndMargo 

On 06/14/2018 02:20 PM, JJ Merelo wrote:
Can you please open an issue in perl6/doc? It's the best to track it, 
and also to check that it's been solved to everyone's satisfaction.


If you can't for any reason, I can open it for you, but I'll have to 
keep coming back to see if it's OK when solved...


here?

https://github.com/perl6/doc

Re: RFE: eval documentation

2018-06-14 Thread JJ Merelo 
Can you please open an issue in perl6/doc? It's the best to track it, and
also to check that it's been solved to everyone's satisfaction.

If you can't for any reason, I can open it for you, but I'll have to keep
coming back to see if it's OK when solved...

El jue., 14 jun. 2018 a las 20:12, ToddAndMargo ()
escribió:

> On 06/14/2018 10:31 AM, ToddAndMargo wrote:
> > Dear Perl6 Developers,
> >
> > https://docs.perl6.org/language/5to6-perlfunc#eval
> >
> > Would you please consider adding
> >
> >   ::('&' ~ $RunSpecific)()
> >   &::($RunSpecific)()
> >
> > to the documentation, as well as an explanation of
> > the error message when using EVAL
> >
> > ===SORRY!=== Error while compiling /home/linuxutil/GetUpdates.pl6
> > EVAL is a very dangerous function!!! (use the MONKEY-SEE-NO-EVAL pragma
> > to override this error,
> > but only if you're VERY sure your data contains no injection attacks)
> > at /home/linuxutil/GetUpdates.pl6:6016
> > --> else { EVAL "$RunSpecific"⏏; }
> >
> > Be sure to turn the "use the MONKEY-SEE-NO-EVAL pragma" phrase into
> > `use MONKEY-SEE-NO-EVAL;` as the sentence is to obscure otherwise.
> >
> >
> > Many thanks,
> > -T
>
>
> Be nice to the alternative
>
>   ::('&' ~ $RunSpecific)()
>   &::($RunSpecific)()
>
> and why in
>
> https://docs.perl6.org/routine/EVAL
>
> too
>
>
> --
> ~~
> Computers are like air conditioners.
> They malfunction when you open windows
> ~~
>


-- 
JJ

Re: RFE: eval documentation

2018-06-14 Thread ToddAndMargo 

On 06/14/2018 10:31 AM, ToddAndMargo wrote:

Dear Perl6 Developers,

https://docs.perl6.org/language/5to6-perlfunc#eval

Would you please consider adding

  ::('&' ~ $RunSpecific)()
  &::($RunSpecific)()

to the documentation, as well as an explanation of
the error message when using EVAL

===SORRY!=== Error while compiling /home/linuxutil/GetUpdates.pl6
EVAL is a very dangerous function!!! (use the MONKEY-SEE-NO-EVAL pragma 
to override this error,

but only if you're VERY sure your data contains no injection attacks)
at /home/linuxutil/GetUpdates.pl6:6016
--> else { EVAL "$RunSpecific"⏏; }

Be sure to turn the "use the MONKEY-SEE-NO-EVAL pragma" phrase into
`use MONKEY-SEE-NO-EVAL;` as the sentence is to obscure otherwise.


Many thanks,
-T



Be nice to the alternative

 ::('&' ~ $RunSpecific)()
 &::($RunSpecific)()

and why in

https://docs.perl6.org/routine/EVAL

too


--
~~
Computers are like air conditioners.
They malfunction when you open windows
~~

Re: RFE: eval documentation

2018-06-14 Thread ToddAndMargo 

On 06/14/2018 10:45 AM, Brandon Allbery wrote:
I think the message is obscure for a reason: the last thing you want is 
for someone to make an insecure module look "safe" by just dropping that 
pragma into it. You want to make them think about what they are doing.


I hate always having to ask about these things.  I feel
sometimes like I am asking others to do my homework.

One of my big issues is that I can not always tell when a word
is being used as its English meaning or its Perl meaning.
If I think it is English, it does not occur to me to look
in the documentation.

Re: RFE: eval documentation

2018-06-14 Thread Brandon Allbery 
I think the message is obscure for a reason: the last thing you want is for
someone to make an insecure module look "safe" by just dropping that pragma
into it. You want to make them think about what they are doing.

On Thu, Jun 14, 2018 at 1:32 PM ToddAndMargo  wrote:

> Dear Perl6 Developers,
>
> https://docs.perl6.org/language/5to6-perlfunc#eval
>
> Would you please consider adding
>
>   ::('&' ~ $RunSpecific)()
>   &::($RunSpecific)()
>
> to the documentation, as well as an explanation of
> the error message when using EVAL
>
> ===SORRY!=== Error while compiling /home/linuxutil/GetUpdates.pl6
> EVAL is a very dangerous function!!! (use the MONKEY-SEE-NO-EVAL pragma
> to override this error,
> but only if you're VERY sure your data contains no injection attacks)
> at /home/linuxutil/GetUpdates.pl6:6016
> --> else { EVAL "$RunSpecific"⏏; }
>
> Be sure to turn the "use the MONKEY-SEE-NO-EVAL pragma" phrase into
> `use MONKEY-SEE-NO-EVAL;` as the sentence is to obscure otherwise.
>
>
> Many thanks,
> -T
>


-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net