On Sun, Apr 29, 2012 at 7:56 AM, Jonathan Swartz <swa...@pobox.com> wrote: > Comments and suggestions for names welcome. Devel::MultiTidy?
I like the Any:: name space for things that offer single interfaces to multiple back-ends. One could argue that Tidying really doesn't fit there though. And that argument could be countered with hypothetical examples involving large projects with different styles, enforced by different tidying engines, for different parts of it, and the desire for the scripts called at check-in time to run the correct tidying engine by looking up per-file metadata. -- In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted using situational ethics.
