Well, the production version of my script doesn't actually rely on strict. Originally, I decided to not include use strict in the production version of the script to allow the script to run faster. But since my script doesn't use any module, it can run on configurations that do not have @INC set up properly, which I'm thinking may happen fairly often.
If I were to include use strict and use Fcntl in the production version of the script in the next version, I wonder how many people who upgrade will give me a call about the problem this exposes. I just don't see a reason why I need to go that route when I can avoid it.
Thanks again.
Richard
In reply to Re^4: Can I include O_CREAT, O_EXCEL and O_WRONLY in my script without always requiring Fcntl?
by rzward
in thread Can I include O_CREAT, O_EXCEL and O_WRONLY in my script without always requiring Fcntl?
by rzward
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |