Re: Re: Module questions

But you don't have to use CGI::Cookie as CGI.pm has the following line of code in its cookie function.

require CGI::Cookie;
[download]

Is that "clever module design"?

Oh, and it's "Perl", not "PERL".

--
<http://www.dave.org.uk>

"Perl makes the fun jobs fun
and the boring jobs bearable" - me

Comment on Re: Re: Module questions Download Code

Replies are listed 'Best First'.
Re: Re: Re: Module questions by runrig (Abbot) on Apr 04, 2001 at 20:50 UTC
The poster asked about mod_perl, so I'll add this: If you ARE using mod_perl, then in the mod_perl startup script, you'll want to include both 'use CGI' and 'use CGI::Cookie', as the cookie module does not seem to get included until runtime (after child processes are forked) even when doing 'use CGI qw(-compile :all);'.	[reply]
Re: Re: Re: Module questions by Anonymous Monk on Apr 05, 2001 at 14:52 UTC
I tried not including CGI::Cookie and only haveing use CGI. Unforunately this did not work. It seems you have to include both.	[reply]
Re: Re: Re: Re: Module questions by runrig (Abbot) on Apr 05, 2001 at 21:57 UTC
That does not seem correct, I ran this: `#!/usr/bin/perl -l -w use strict; use CGI qw(:all); print for keys %INC; my $c = cookie('bob'); print "--------"; print for keys %INC;` [download] And got these results: `$ ./tst \| grep "^[C-]" Carp.pm CGI/Util.pm CGI.pm -------- Carp.pm CGI/Util.pm CGI/Cookie.pm CGI.pm` [download] So using just 'CGI' SHOULD work and load the CGI::Cookie module when you call the cookie function.	[reply] [d/l] [select]
Re: Re: Re: Module questions by satchboost (Scribe) on Apr 04, 2001 at 21:47 UTC
Fair enough. That is clever module design. I suspect that it's also common module design, but it's not something that a beginner, as the poster indicated s/he was, would think about. In addition, it's listed among the common mistakes someone from C++ would make coming to PERL(!). It's certainly not what I thought about when I first started working on modules. And as long as you understood what I was talking about, it could've been peRl, Per1, or PerL. grins I don't want to start a flamewar, but that did seem a little nitpicky.	[reply]