maybe the fastest possibility to find such a bug without knowing the last healthy state:

• use perltidy to indent the whole file, should generate a separate .tdy file by default
• grep all occurrences of "{" and "}" into a separate file
• go to the end of file and scroll back till the indentation looks normal

I tried this with a 30k lines module and the output had 5k lines.

you'll get something like this which is easier to be checked visually:

One extra hint: since nesting subs is rare in Perl I'd also grep for sub keywords which are (unusually) intended.

That's only 600 lines in this case.

Apply perltidy -csci=0 -csc for "closing side comments" everywhere to identify the closing } of sub, if, etc.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.