Mark Stosberg wrote:
When Perl 5 has references and Perl 6 doesn't, I don't know what to
expect to when I need to pass a hash reference to a Perl 5 routine.
Such details make no appearance currently in the Perl 6 spec, but I'm
trying to gather them on the wiki if you have anything to add
Juerd wrote:
It does make sense to have a single toolkit that does all this. It does
not make sense to have a single .pm that does all this. There's
absolutely no need for having all these different tasks in one module.
There's not even any benefit. You can just as well use a couple of
Aankhen wrote:
The major feeling was that there should be no CGI.pm (if someone was
hellbent on using it, they could use the Perl 5 module).
In theory, use perl5:CGI could be a fine solution. In practice, it
hasn't worked out well for me. Even something that seems simple like
passing a
I agree completely. In that vein, I think that one thing a lot of web
developers would like to have available more easily would be session
management. In PHP it's as simple as $_SESSION['key'] = 'value'. I
understand that CGI.pm is a fundemantally different concept from PHP and
that
Juerd wrote:
Personally, I am *against* HTML generating for elements that are not
form fields. And for form fields, I think the solution should be in the
templating thing, not elsewhere. Stickiness makes sense on invalid data
only anyway, and we need to put the error message and a pointer
Aankhen wrote:
The major feeling was that there should be no CGI.pm (if someone was
hellbent on using it, they could use the Perl 5 module).
In theory, use perl5:CGI could be a fine solution. In practice, it
hasn't worked out well for me. Even something that seems simple like
passing a
Darren Duncan wrote:
P.S. I originally sent this to just Mark Stosberg yesterday, and he
suggested I sent it to perl6-users for more exposure, so here it is,
slightly edited.
And here is my reply to Darren, slightly edited.
I'm only interested in CGI.pm so much as it holds up my work on
CGI
First, what's the recommended reference for learning how dispatching to
the right 'multi' sub is resolved. ?
I'd like to know the expected behavior in this case:
multi sub foo () { say b: }
multi sub foo () { say a: }
foo();
I would expect it would throw an error or at least a warning, since
