}
}
- # Make the output file writable unless we are in -b mode.
- # The reason is that perltidy does not unlink existing
- # output files before writing to them, for safety, so if an
- # existing output file is marked not writable then perltidy
- # will stop. This can prevent a disaster for a user who
- # accidentally enters "-o important_data", but it also
- # means that perltidy may fail when rerun with its default
- # output file unless it marks its own output files
- # writable. The alternative, of always unlinking the
- # designated output file, is unsafe, except in -b mode,
- # where there is an assumption that a previous backup can
- # be unlinked even if not writable.
+ # Make the output file writable unless we are in -b mode.
+ # The reason is that perltidy does not unlink existing
+ # output files before writing to them, for safety, so if an
+ # existing output file is marked not writable then perltidy
+ # will stop. This can prevent a disaster for a user who
+ # accidentally enters "-o important_data", but it also
+ # means that perltidy may fail when rerun with its default
+ # output file unless it marks its own output files
+ # writable. The alternative, of always unlinking the
+ # designated output file, is unsafe, except in -b mode,
+ # where there is an assumption that a previous backup can
+ # be unlinked even if not writable.
if ( !$in_place_modify ) {
$output_file_permissions |= oct(600);
}