Jonathan Scott Duff wrote: > > My first thought was "this should definitely be in a module" and your > comments just fire those synapses even more strongly. Yes, this will likely end up in a core module. The main thing is that it always has to be available so that pragmas like "use cgi" can import it. -Nate
- RFC 333 (v1) Add C<header> and C<unheader>... Perl6 RFC Librarian
- Re: RFC 333 (v1) Add C<header> and C<unh... John Barnette
- Re: RFC 333 (v1) Add C<header> and C<... Jonathan Scott Duff
- Re: RFC 333 (v1) Add C<header> and ... Nathan Wiger
- Re: RFC 333 (v1) Add C<header> and C<unh... Philip Newton
- Re: RFC 333 (v1) Add C<header> and C<... Nathan Wiger
- Re: RFC 333 (v1) Add C<header> and ... Philip Newton
- Re: RFC 333 (v1) Add C<header> and C<unh... Alan Gutierrez
- Re: RFC 333 (v1) Add C<header> and C<unh... Alan Gutierrez
- Re: RFC 333 (v1) Add C<header> and C<unh... Alan Gutierrez
- Re: RFC 333 (v1) Add C<header> and C<... Nathan Wiger
- Re: RFC 333 (v1) Add C<header> and C<unh... Jerrad Pierce
- Re: RFC 333 (v1) Add C<header> and C<... Nathan Wiger