On Tue, Dec 28, 2010 at 12:25 PM, Jon <jon.forums@gmail.com> wrote:

> I think it's fine to enforce code consistency for MRI core and it's included extensions, but agree with you on breaking third party code. I can't yet see how this mod enhances code quality. Extension API's already exist for third parties to code to. IMO, a build flag is not an API.
>

Jon, why not report this to Ruby-Core instead?

If the flag is going to have such impact on extensions and other gems,
Core should hear this before that change hits another release.

More than "extending things to circumvent the change" in the form of
patch or anything, better tell Core to revert that or make it default
false with the optional configure flag.

Sorry for the tone, couldn't resist that this needs to be deal on Core
by Core and not discussed over this list.

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry