I use it constantly, on every single piece of code I write that's longer than a command-line. I've never had a single problem with it. Have you reported the bugs you've found? | [reply] |
No, it was before I got into the swing of things with reporting bugs and such. I just don't trust the thing anymore especially since it is a perl parser.
| [reply] |
You do seem to use some pretty unusual code, based on things I've seen you post on perlmonks, so that could be the issue. You're still the first and only person who I've ever heard complain about bugs from perltidy though.
| [reply] |
I just don't trust the thing anymore especially since it is a perl parser.
I'd give it another whirl. Maybe there have been bug fixes since you last used it.
It's certainly part of my standard Perl toolkit. I've used it a lot on large piles of evil code and have yet to have a problem.
| [reply] |
I don't use it often, but I've never had a problem with it personally. I mainly use it for downloaded code where the formatting was screwed up somehow. Sometimes, though, it has helped me to find a forgotten closing brace or some similar syntax mistake on my part. | [reply] |
I read the warnings about Perltidy, but the only problem it gives me is formatting that I didn't ask for. I don't think it should be used on a large script that's not easy to test afterwards.
All I use is:
cd directory_of_PerlTidy
perl perltidy -io -i=3 path_to_script_to _be_formatted
I keep the above in a comment in the script it's used in. There should be a feature to automatically insert such a comment, with a time stamp of when it was titied. | [reply] |
cd directory_of_PerlTidy
perl perltidy -io -i=3 path_to_script_to _be_formatt
+ed
I keep the above in a comment in the script it's used
in. There should be a feature to automatically insert such
a comment,
If there's some boiler-plate that you want to appear in all
of your code, you need an emacs templating system, such as
template.el:
-
http://emacs-template.sourceforge.net/
I've been working on an emacs lisp package to use
template.el with perl, which I call "perlnow.el":
-
http://obsidianrook.com/perlnow
Even if you don't want to use my code, you might like to
look at the template.el templates there that I set-up to
use for perl code.
(Briefly: perlnow.el is designed to automate some routine
tasks in perl programming: jumping into writing code,
doing a "compile/check" on the code, jumping into writing
tests for your code, running the tests, and so on. I've
been finding it useful, but I'm still turning up minor bugs.)
with a time stamp of when it was tidied.
There I can't help you much off hand, you'll need to do
some hackery of your own, either in perl or elisp.
What I would probably do is write some elisp similar to
what rhythmicus posted: it wouldn't be too hard to
write an emacs extension that would do a perltidy on
the current buffer, and insert or update a standard
comment with a timestamp for when perltidy was run.
20040810 Edit by ysth: move </i> out of <blockquote> | [reply] [d/l] |