Skip Menu |

This queue is for tickets about the Config-General CPAN distribution.

Report information
The Basics
Id: 42331
Status: resolved
Priority: 0/
Queue: Config-General

People
Owner: tlinden [...] cpan.org
Requestors: fbicknel [...] nc.rr.com
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 2.42
Fixed in: (no value)



Subject: Documenation conflict around -StrictObjects
Sayeth the Config::General docs: If you turn -StrictObjects off (by setting to 0 or "no") it will just return an empty object/hash/scalar. Sayeth the Cofngi::General::Extended docs: You can turn this behavior off by setting -StrictObjects to 0 or "no". In this case undef will be returned. It turns out that the code emulates the former, rather than the much more useful latter behavior. It would be nice if the second behavior were emulated, for it is much more useful to know without calling $o->exists ('widget') whether an item exists in the configuration. One could simply call $o->widget and act on the return value (if undef, it's not there: if '', then it's there, but empty.)
oops, this is 2.42 where I noticed this.
Oh, perfect! Change line 318 in General/Extended.pm to: return undef; ... and it works! DB<43> x $self->DEPORT 0 undef DB<44> x $self->NODEPORT 0 '' DB<45> I'll keep using this patch and see if it indeed has no other flaws, but I may have just cured it. :) Cheers.
Here's another one in Config::General docs (more trivial stuff) -AllowMultiOptions If the value is "no", then multiple identical options are disallowed. The default is "yes". i.e.: -AllowMultiOptions => "no" It says the default is 'yes', then shows an example with 'no' supposedly showing the default.
fixed in 2.43