-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update perlfunc.pod to document die newline workarounds #22037
base: blead
Are you sure you want to change the base?
Conversation
Else the user cannot find where the program died! Welcome to enhance my patch.
What does a user care where a program died? |
Because s/he might have 50 files, each with 50 die statements, and finding which one died would be a nightmare. |
It's only a nightmare to find which You really have two problems bumping up against each other here and it mostly goes away if, as a point of order, you include a label before you I usually sub-class which ever logger the project uses with a $app->log->labelled_dump( customer_credit_carrds => \@cards );
# Tue 27 [9203] request=b4dc0ffee [debug] customer_credit_cards [{type => amex.... Even in a single-file script using |
The very very very very main source of problems, is the person way back one who thought it would be smart to make things act different depending on a final new line. It might have seen like a cool idea way back when. But sure enough ... Also one can I just use $. In here-documents, and then getting the file name is a big drag too. So okay you guys are welcome to put your ideas into the die documentation too. |
Maybe you can write a perlcritic role to prevent this being done on accident if your own code? |
I don't want to change the code. But workarounds should be documented for when |
Yeah I don't think this is a good idea either |
Else the user cannot find where the program died!
Welcome to enhance my patch.