That's not trivial without knowing the previous version.

apart of using version control (like already mentioned)

For instant feedback

• run perl -c continuously in the background ( e.g. flycheck in emacs, default in Komodo)
• use automatic indentation while typing

For delayed analysis

• jump thru the last edits your editor recorded ( goto-last-change in emacs )
• indent the whole file, use perltidy if your editor doesn't support this ( indent-region in emacs) and do a visual check
• diff with the backup file your editor generated
• use tybalt89's suggestion to jump to the opening curly parsed by the editor for every closing one you find

update

perltidy has some additional features for code analysis, have a look.

IIRC there is also one to add extra info in a comment after each closing block.

---

---

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.