From: Nicholas C. <ni...@un...> - 2003-01-25 13:50:43
|
On Fri, Jan 24, 2003 at 08:16:11PM -0500, Wizard wrote: > > I would have thought it would be better to have a single method that > > returns 1 if it's true or 0 if it's false. > > Yeah, you're probably right. I just kinda like code that looks like: > if( $cfg->is_false( 'Threading' ) ) {... > > rather than: > if( !$cfg->state( 'Threading' ) ) { ... > > It seems more readable. I really didn't think about it being a problem if it > failed to match either, but that's because I was writing it ;-). How about > is_true and I'll check inverse values? i.e., > return undef if !/^[Yy]|[Tt]|[Oo]n|[1]/ > and !/^[Nn]|[Ff]|[Oo]ff|[0]/; > That way the application can choose to die or offer alternative execution > paths. The other option being as you stated, dying inside the module. I > never really liked that though, because it limits what the programmer can do > without editing the module. Surely the perlish way to do this is 1 if it's true (/^[Yy]|[Tt]|[Oo]n|[1]/) 0 if it's false (/^[Nn]|[Ff]|[Oo]ff|[0]/) and undef otherwise? Nicholas Clark |