|
in reply to Re: Error Log Files
in thread Error Log Files
I am assuming that this code compiles and resides in memory
and each time an error or warn is captured it is sent through carpout to be printed.
So if I put print "\n\n"; after the carpout call, it should insert a blank line.
However, based on the next monk response, carpout does not work that way and output the whole black of error in one shot
and the blank is added befor eor after the block depending location of the \n\n code. |
Re^3: Error Log Files
by 1nickt (Canon) on Mar 07, 2017 at 15:41 UTC
|
So if I put print "\n\n"; after the carpout call, it should insert a blank line.
What in the documentation for carpout supports that idea? More doc, less assuming!
Since the BEGIN block is executed at the beginning only, as explained in its documentation, maybe what you are thinking of is a custom sig handler for warn?
The way forward always starts with a minimal test.
| [reply] |
|
|
So basically it opens a path to "mylogfile" where the errors are written so obviously \n\n is meaning less in this case.
Adding blank lines would have to take place in the actual module code. Ug!! Read and UNDERSTAND documentation.
Thanks
| [reply] |
|
