Jifty::Manual::Style3pm

Jifty coding style guide default style when in doubt, default to whatever damian conway's perl best practices says. private documentation when documenting a private method, or providing documentation which is not useful to the user of the module (and is presumably useful to the developer), wrap it in =begin/end private. this way it does not show up in perldoc where a user would see it and yet is still available and well formatted (that is, not just a lump comment) when looking at the code. test temp files files created by tests should be declared as such using jifty::test->test_file() so they are cleaned up on a successful test run. use shell::command shell::command has a number of functions which work like common shell file commands such as "touch", "cp" and "mv". they are battle tested and cross-platform. use them instead of coding your own. for example, instead of this: do this: case insensitive matching to check if a string equals another string case insensitively, do this not this: