On Nov 27, 2010, at 09:35 , Chauk-Mean Proum wrote:

> Issue #4085 has been updated by Chauk-Mean Proum.
>=20
>=20
>>> Regarding naming: how about using the name `use' instead of `using'? Th=
is
>>> would be in line with other names such as `include', `extend', etc.
>=20
>> Some other people said the same, but I think `using' is better than
>> `use' because `use' is already used in Rack.
>=20
> IMHO, it would be a shame to have such a new core feature with a "strange=
" naming.
> I also prefer use instead of using.
> May be the core team can request Rack developers to rename their use meth=
od to e.g. rack_use.
> I guess that this new feature will be available only for ruby-1.9.3+.
> So this leaves time for Rack developers and users to migrate their code b=
ase.

This would be about any Ruby web application/framework/library out there. N=
ot only Rack implements use, but Rails and Sinatra (and probably others) do=
 so, too, in order to behave like Rack.

Konstantin