QUERY_STRING parsing for DELETE method in CGI.pm
…st and patched the associated pod
…st and patched the associated pod.
which allows us to drop an exception targeted directly at Perl 5.8.0.
5.8 has been out almost 10 years.
CGI.pm requires 5.6 or higher now, so this is implied.
It appears this "require utf8" line was here to support the following call to "utf8::encode". However, the documentation is clear this is not required, and I believe this line effectively did nothing.
This chunk of code was only called for Perl < 5.6, but we already require at least Perl 5.6, so this code was not supported and should not have been accessed.
Thanks to Dave Rolsky for the nudge.
…ied. RT#64261, thanks to Niko Tyni
That commit was "196ab302c0db40647a438b01f0e8027ab8efc21d" The commit removed "use CGI" from CGI::Cookie, to decouple the modules. However, it turns out that bake() requires CGI.pm, but there were no tests for that. This patch "requires" CGI.pm on demand when bake() is called. A reality-check test for bake() was also added, which insures that CGI.pm is loaded when it is called.
The meaning is the same. The code style is taken from CGI::Simple::Cookie.
The whitespace behavior is now identical to CGI::Simple::Cookie, and has an automated test.
and test and document the prior behavior when the return value is missing. The new short-circuit logic is cleaner but equivalent, and avoids emitting an "unitialized string" warning. Thanks to Yanick for suggesting this direction.
This behavior mimics CGI::Simple, and catches potential garbage-in/ garbage-out program.
The goal is to reduce the "diff" of code between CGI.pm and CGI::Simple, so some non-meaningful code-style differences are being eliminated. This makes it easier to confirm when the two modules are actually different.