Re^4: Date::Day issues

Replies are listed 'Best First'.
Re^5: Date::Day issues by cdarke (Prior) on Mar 25, 2010 at 08:52 UTC
Your printf statement does not appear in the original code that you copied, and claim to be the source of the problem. Is the output file empty, and has the date/time stamp been updated? Are you testing the open to check that the file handle is created? Are you running with `use warnings;` and `use strict;`? Do you not have a test system? If you don't then this might be a good time to justify having one.	[reply] [d/l] [select]
Re^6: Date::Day issues by Conal (Beadle) on Mar 25, 2010 at 11:30 UTC
yes the file is being created , but for whatever reason printf isnt putting anything into it. i am just changing the code to show the date as a day with that method from Date::Day, the original source just prints the day and date in numbers. And that works just fine. I dont have a test system, no.. its a relatively complex set of applications of which the perl script is just one component. The perl script doesnt have `use warnings;` and `use strict;` The code is all a little hacky tbh, its something i wrote years ago. I guess i should sit and down and sort it all out once and far all.. but the systems i use here rely on it running 24/7. But i will take your advice and try and think of creating some kind of test environment. thanks. conal.	[reply] [d/l] [select]
Re^7: Date::Day issues by cdarke (Prior) on Mar 25, 2010 at 12:29 UTC
It could be the printf statements are "not working" or, because of some conditional statement that you have not shown, maybe they are not being executed at all? Your original question was about the 'day' subroutine, maybe one of the other modules you included also exports a subroutine of the same name which does something else? You could try a simple test script just using all those modules set with `use warnings; use strict;` as see if you get any error messages about subroutines being redefined.	[reply] [d/l]
Re^5: Date::Day issues by ikegami (Patriarch) on Mar 25, 2010 at 08:25 UTC
How did you check if the print succeeded if you didn't run it. I didn't say anything about outputting the error to the console. But then again, you're asking about printing problems. I didn't say anything about touching your live script. Recreate the problem with another script. You might have to execute it in a manner similar to your live script if it's a permission issue. Note: If the file isn't being created, it's not likely that the `print` is the culprit. Check the result of `open`.	[reply] [d/l] [select]