Re: RFC: a universal tidier
Devel::MultiTidy? https://pause.perl.org/pause/query?ACTION=pause_namingmodules#Avoid_the_too_general_nouns_like_Dev I suggest top-level `Code` instead, it is already in use: cpan[1] d /[/]Code/ DistributionALFIE/Code-Dumper-0.01.tar.gz DistributionANDREWF/CodeBase-0.86.tar.gz DistributionCODECHILD/XML-Bare-0.07.tar.gz DistributionCODECHILD/XML-Bare-SAX-Parser-0.01.tar.gz DistributionCODEHELP/XML-QOFQSF-0.05.tar.gz DistributionFDALY/Code-Perl-0.03.tar.gz DistributionFRANCISCO/CodeManager-0.02.tar.gz DistributionKITOMER/Code-Class-C-0.08.tar.gz DistributionMITHALDU/Code-Statistics-1.112980.tar.gz DistributionNAZRI/Code-Generator-Perl-0.03.tar.gz DistributionSWALTERS/Code-Splice-0.01.tar.gz DistributionSZABGAB/Code-Explain-0.02.tar.gz 12 items found signature.asc Description: PGP signature
Re: RFC: a universal tidier
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.
Re: RFC: a universal tidier
Yeah, Any::Tidy seemed to suggest to me use the best of available tidiers. I'm leaning now towards Devel::TidyAll, with tidyall being the name of the script. On Apr 30, 2012, at 11:17 AM, David Nicol wrote: 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.
RFC: a universal tidier
I'm thinking about a module/script to unify a bunch of code tidiers and validators in a single place. With a single command, e.g. % tidyall you could apply the appropriate tidiers and validators to files in your project (e.g. your git directory hierarchy). It would tidy each file as needed and throw an error result if any of the validations failed. Features: * Only tidy files that haven't changed since the last time (using File::Modified and a file cache) * A single config file with options for all the tidiers and validators, as well as which files to apply them to * Easy to add new validators/tidiers as plugins This would be a command that the anal-retentive among us could run on our projects before each commit. Tidiers and vaildators for Perl include Perl::Tidy, Pod::Tidy, and Perl::Critic. There are also various tidiers and validators for HTML, css and javascript out there. Comments and suggestions for names welcome. Devel::MultiTidy? Thanks Jon
