Bill Moseley wrote:
In 2.14 Template::Plugins::_load did this:if ($module = $self->{ PLUGINS }->{ $name }) { 2.15 now does: if ($module = $self->{ PLUGINS }->{ $name } || $self->{ PLUGINS }->{ lc $name }) { which caught me because I had a plugin (relative to PLUGIN_BASE) that shared a name with a $STD_PLUGINS plugin, only different in case. So upon upgrading TT was loading the standard plugin instead of my customized one. That's probably my fault for using s similar name (or not using PLUGINS hash to define my plugin). Is case not important when loading plugins defined in the PLUGINS hash? Andy, you using OSX now?
This was a change done on purpose. I sent in a patch that would allow TT operators to configure TT to use plugins in a case insensitive fashion. Andy, decided it should just be standard behavior. I think that is probably the correct thing to do, since TT should cater to a "simpler" crowd, and as such case shouldn't matter. Having two different affects from one name would just confuse people anyhow. -- Josh _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
