[Templates] Case of default plugins in 2.15

[Bill Moseley]

On Mon, Sep 18, 2006 at 02:43:54PM -0600, Josh Rosenbaum wrote:
> 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 }) {
> 
> 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.

Well, there's still two different behaviors.

The case only doesn't matter for built-in plugins or plugins defined
with PLUGINS config option.  But, plugins loaded otherwise can be case-dependent
on some platforms.

I guess if you code on Windows or OSX hfs you have to be careful about
file names in general if you expect to move the application to a file
system that does care about case.


-- 
Bill Moseley
moseley@hank.org