Ian Langworth wrote:
It sounds like the name of HTTP is more appropriate:
HTTP::Request
...uri, pathinfo, params, method, headers, etc.
HTTP::Request::Session
...adds to HTTP::Request to provide session() method
HTTP::Response
...response code, content, headers, etc.
Fagyal Csongor schrieb:
Ian Langworth wrote:
A general, simple CGI handling module fits into 200 lines, including
POD.
[..]
You don't really need more. IMHO a CGI module
parses/preprocesses/decodes/etc. all incoming parameters (POST, GET,
COOKIES), and that's it.
I can support this
Fagyal Csongor skribis 2006-09-20 11:28 (+0200):
You rarely do real HTTP handling when you use CGI.
You may not, but many people do a lot of these things.
And when you don't, the datastructures are currently parsed and filled
anyway, so I don't know why you say it'd be too inefficient.
A
Erm...
Sorry for the bandwith usage again, but what about something like
class CGI
is CGI::Base
does CGI::ParamParser
does CGI::HTML
{ ... }
?
To make CGI.pm kind of backward compatible, but separates the layers.
(Please excuse my bad syntax/semantics.)
- Fagzal
Fagyal Csongor wrote:
# imagine something like:
$cgi = new CGI;
$html = HTML::CGI-new($cgi);
$html-popup_menu( ... ); # I won't do this, but others might... :)
My biggest gripe with CGI's html methods is the inconsistency in their
names. I use them every now and then, but I always have
Jacinta Richardson skribis 2006-09-21 0:13 (+1000):
My biggest gripe with CGI's html methods is the inconsistency in their
names. I use them every now and then, but I always have to go and look
up the documentation. It's textfield isn't it? So that would make
this one passwordfield: nope,
Thanks for help. For anyone else, the following works.
sub infix:grew_by_to {...};
(32 grew_by_to 48).say;
sub infix:grew_by_to ($left, $right) {
return ($right/$left - 1) * 100 ~ '%';
};
Yuval Kogman wrote:
On Sun, Sep 17, 2006 at 16:35:39 +0100, Daniel Hulme wrote:
What am I doing
Juerd wrote:
[...]
Fagyal Csongor skribis 2006-09-20 15:43 (+0200):
Inefficient was probably a bad choice of word.
I would rather say: I would not like to see Perl6's CGI.pm as a monster
module, which has one part everyone uses, and one hundred other parts
that some uses, because I feel
Hi,
I was wondering if there is (or there should be) a documentation on how
to elegantly write Perl6 code.
I am afraid that when I will be starting to write Perl6 code, it will be
too much Perl5-ish, and I will end up rewriting my code in every 3
months because I hate when my code is not
On 9/20/06, Fagyal Csongor [EMAIL PROTECTED] wrote:
I was wondering if there is (or there should be) a documentation on how
to elegantly write Perl6 code.
yes, there should be.
I am afraid that when I will be starting to write Perl6 code, it will be
too much Perl5-ish, and I will end up
* Juerd [EMAIL PROTECTED] [2006-09-20 22:25]:
I think it's time we moved away from the param method, and
started using a hash.
I don’t know about that. The `param` method has the nice property
that it allows you to pretend everything’s a single value or to
use multi-valued params, at your own
A. Pagaltzis schrieb:
On top of this, roughly 80% (or so it sometimes feels)
of the useful attributes defined in HTML do not have any tangible
browser support (such as `cite` on `blockquote`/`q`, or
`datetime` on `ins`/`del`).
At least without CSS. You can use those tags to create a more
On Thu, Sep 21, 2006 at 12:43:41AM +0200, Juerd wrote:
: my @bar = @{ $q-param-{ 'bar' } };
:
: my @bar = $q.parambar.'@';
: my @bar = @ $q.parambar;
That should work but my preference is just
my @bar = $q.parambar[];
That is, empty .[] has the same arrayifying semantics as @. (This
On 9/20/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
I did qualify my statement.
I'm sorry, I must have missed it. :-)
Aankhen
14 matches
Mail list logo
