Dan Sugalski wrote: > > >Because taint mode needs to be turned on REEELY early, like before > >pragmas are compiled. > > 'no taint' does make sense, though 'use taint' might not except to locally > undo 'no taint'. Actually, from my talks with Larry both on and off-list about this, he convinced me pretty strongly that the only thing that really makes sense is untainting data sources. And this should be done via $fh->untaint, which already exists. The original email was here: http://www.mail-archive.com/perl6-language@perl.org/msg00394.html Follow the thread a little for details. A "no taint 'checking'" seems like an interesting idea, but I'm not sure providing lots of ways around tainting is what we want... -Nate
- Re: RFC 288 (v2) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Hildo Biersma
- Re: RFC 288 (v2) First-Class CGI Support Alan Gutierrez
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support iain truskett
- Re: RFC 288 (v2) First-Class CGI Support Alan Gutierrez
- Re: RFC 288 (v2) First-Class CGI Support James Mastros
- Re: RFC 288 (v2) First-Class CGI Support Adam Turoff
- Re: RFC 288 (v2) First-Class CGI Support Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI Supp... James Mastros
- Re: RFC 288 (v2) First-Class CGI ... Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI ... Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI ... Dan Sugalski
- Re: RFC 288 (v2) First-Class CGI Support James Mastros
- Re: RFC 288 (v2) First-Class CGI Support Robert Mathews
- Re: RFC 288 (v2) First-Class CGI Support Nathan Wiger
- Re: RFC 288 (v2) First-Class CGI Support Robert Mathews
- Re: RFC 288 (v2) First-Class CGI Support Alan Gutierrez