Bug #18890 for Class-CGI: Typo in POD: Congif::Std referenced instead of Config::Std

Sun Apr 23 10:34:50 2006 Guest - Ticket created

Subject:

Typo in POD: Congif::Std referenced instead of Config::Std

In POD for lib/Class/CGI.pm section "Creating a profile file", apparent typo references module 'Congif::Std'. Suggest should be 'Config::Std'. Patch attached.

Subject:

update_pod.patch

--- CGI.pm Sat Apr 22 15:51:18 2006 +++ CGI-new.pm Sun Apr 23 09:26:32 2006 @@ -683,7 +683,7 @@ For larger sites, it's not very practical to replicate this in all code which needs it. Instead, C<Class::CGI> allows you to define a "profiles" file. -This is a configuration file which should match the C<Congif::Std> format. At +This is a configuration file which should match the C<Config::Std> format. At the present time, only one section, "profiles", is supported. This should be followed by a set of colon-delimited key/value pairs specifying the CGI parameter name and the handler class for the parameter. The above import list

Sun Apr 23 15:56:40 2006 ovid [...] cpan.org - Taken

Sun Apr 23 15:59:10 2006 ovid [...] cpan.org - Correspondence added

On Sun Apr 23 10:34:50 2006, guest wrote: Show quoted text

> In POD for lib/Class/CGI.pm section "Creating a profile file", apparent > typo references module 'Congif::Std'. Suggest should be 'Config::Std'. > Patch attached.

Thanks! This is now corrected and will be released with the next version. However, I'm not sure when that release will be due to a major security hole in a dependency. See http://use.perl.org/~Ovid/journal/29418 for more details. Cheers, Ovid

Sun Apr 23 15:59:11 2006 The RT System itself - Status changed from 'new' to 'open'

Tue Apr 25 10:34:01 2006 darren.meyer [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #18890] Typo in POD: Congif::Std referenced instead of Config::Std
Date:	Tue, 25 Apr 2006 09:33:14 -0500
To:	bug-Class-CGI [...] rt.cpan.org
From:	"Darren Meyer" <darren.meyer [...] gmail.com>

As I mentioned in my PM /msg (I'm RadiantMatrix), I've run into that issue before, with little success dealing with it. I was thinking a bit, though, and I'm wondering if a simpler problem might serve you well. Your goal is really to check for the *existence* of modules, not necessarily that they have a certain version, or work, right? If so, wouldn't following be sufficient? use File::Spec::Functions qw[catfile]; sub module_exists { my $module_name = shift; my @parts = split('::',$module_name); $parts[-1].='.pm'; for (@INC) { return 1 if -f catfile($_,@parts) } return 0; } In other words, just checking to see if the module *exists* in @INC? If not, I'd be interested in why not -- always willing to learn from the more experienced. Cheers, radiant On 4/23/06, via RT <bug-Class-CGI@rt.cpan.org> wrote: Show quoted text

> > <URL: http://rt.cpan.org/Ticket/Display.html?id=18890 > > > On Sun Apr 23 10:34:50 2006, guest wrote:

> > In POD for lib/Class/CGI.pm section "Creating a profile file", apparent > > typo references module 'Congif::Std'. Suggest should be 'Config::Std'. > > Patch attached.

> > Thanks! This is now corrected and will be released with the next > version. However, I'm not sure when that release will be due to a > major security hole in a dependency. See > http://use.perl.org/~Ovid/journal/29418 for more details. > > Cheers, > Ovid >

-- Darren Meyer darren.meyer@gmail.com "In work, be competent" - Tao te Ching, verse 8. The opinions expressed above are my own, and do not necessarily reflect my employers', friends', spouse's, or cat's.