perltidy

Started by Peter Eisentrautalmost 15 years ago4 messageshackers
Jump to latest
#1Peter Eisentraut
peter_e@gmx.net

How much do we care about applying perltidy, as described in
src/tools/msvc/README, everywhere? I just ran it across the entire
tree, using

perltidy -b -bl -nsfs -naws -l=100 -ole=unix **/*.pl **/*.pm

and it generated 6531 lines of (unified) diff, of which 357 are in
src/tools/msvc/ itself. So clearly it's not being applied very
consistently.

Given how easily this appears to work and how we're sneakily expanding
the use of Perl, I think we ought to add this to the standard pgindent
routine.

#2Bruce Momjian
bruce@momjian.us
In reply to: Peter Eisentraut (#1)
Re: perltidy

Peter Eisentraut wrote:

How much do we care about applying perltidy, as described in
src/tools/msvc/README, everywhere? I just ran it across the entire
tree, using

perltidy -b -bl -nsfs -naws -l=100 -ole=unix **/*.pl **/*.pm

and it generated 6531 lines of (unified) diff, of which 357 are in
src/tools/msvc/ itself. So clearly it's not being applied very
consistently.

Given how easily this appears to work and how we're sneakily expanding
the use of Perl, I think we ought to add this to the standard pgindent
routine.

Yes, I would support that.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

#3Magnus Hagander
magnus@hagander.net
In reply to: Bruce Momjian (#2)
Re: perltidy

On Tue, Jun 14, 2011 at 21:39, Bruce Momjian <bruce@momjian.us> wrote:

Peter Eisentraut wrote:

How much do we care about applying perltidy, as described in
src/tools/msvc/README, everywhere?  I just ran it across the entire
tree, using

perltidy -b -bl -nsfs -naws -l=100 -ole=unix **/*.pl **/*.pm

and it generated 6531 lines of (unified) diff, of which 357 are in
src/tools/msvc/ itself.  So clearly it's not being applied very
consistently.

Given how easily this appears to work and how we're sneakily expanding
the use of Perl, I think we ought to add this to the standard pgindent
routine.

Yes, I would support that.

I think I suggested that before at some point, but can't find the
reference. But that means, +1.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

#4Bruce Momjian
bruce@momjian.us
In reply to: Peter Eisentraut (#1)
Re: perltidy

Peter Eisentraut wrote:

How much do we care about applying perltidy, as described in
src/tools/msvc/README, everywhere? I just ran it across the entire
tree, using

perltidy -b -bl -nsfs -naws -l=100 -ole=unix **/*.pl **/*.pm

and it generated 6531 lines of (unified) diff, of which 357 are in
src/tools/msvc/ itself. So clearly it's not being applied very
consistently.

Given how easily this appears to work and how we're sneakily expanding
the use of Perl, I think we ought to add this to the standard pgindent
routine.

I have moved the Perl indentation command-line docs into the pgindent
README and it will be run as part of the pgindent checklist. Applied
patch attached.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Attachments:

/rtmp/perltext/x-diffDownload+4-6