Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^5: Why isn't a fatal error trappable?

by perl-diddler (Hermit)
on Aug 02, 2012 at 19:50 UTC ( #985098=note: print w/ replies, xml ) Need Help??


in reply to Re^4: Why isn't a fatal error trappable?
in thread Why isn't a fatal error trappable?

I don't think people realized what I was saying above --

The routine normally works.

I.e. I've looked over my code base and find no instance of SIG{DIE} or SIG{WARN}, but all say SIG{__DIE__} and SIG{__WARN__}...

In talking about it/typing it in, I left off the extraneous bits as I was stating that it WAS working (which it wouldn't if I had not used the double-underscore brackets.

Thus correcting how I spelled a reference to the perl features SIGDIE and SIGWARN handlers, the I thought the exact spelling was did nothing to clarify why it only failed in the one case.

Given people's response to my statement, that focusing on 'spelling' mistakes in my problem statement didn't really help solve the problem. They probably felt I was blowing off a syntactical correction, but I thought it was clear that wasn't the issue when I said (works for other cases...)...so... I gave up after getting those reviews (on this question).... It's good to know it worked for someone -- maybe they had a different perl version.

Having people nit pick over spelling when the spelling isn't in the code, is frustrating and time wasting. It's also takes alot more time for me to look up every line of code and cut/paste it in, rather than, in some cases, answer from memory...(depends on situation)...

I wanted to clarify that I wasn't blowing off the syntactical correction, just the need to talk about a syntactical correction based corrections when I needed semantic solutions. Instead, exactly what I feared happened happened, aided in part by me! I.e. everyone's attention was drawn to the non-problem of the syntax issue and my be assertion that doing so was a classic case of obfuscating or (in this case) derailing discussion of the real problem.

Not that this problem is of any importance anymore. But that's sometimes why I try to focus attention on specific areas by showing partial examples -- just like I didn't need spelling corrections, I was afraid people would criticize other aspects of my code that were working fine because they didn't follow somebody else's idea of "best practices"...way too big an issue for me to get into...

problem is, I can either post and talk about these issues, or I can solve them. too often I spend way too much time talking about an issue or justifying why I did something that was entirely unrelated to the problem I was trying to solve.

Some then come up with the idea that if I didn't code that way, I wouldn't have the problem -- well If I didn't code, I wouldn't have the problem either, but neither achieves the goal of getting the existing code working. Sometimes we have our quirks and ways of doing things (you say tomayto, they say tomahto...etc))...

People can focus all day on the superiority of being half black on the left or the right (being white on the other) side. Doing so created harmful differences that prevented them from working together. Such situations are sad, if not pathetic no matter if you are on one of the parties or a watcher...

2


Comment on Re^5: Why isn't a fatal error trappable?
Re^6: Why isn't a fatal error trappable?
by Corion (Pope) on Aug 02, 2012 at 20:00 UTC
    Having people nit pick over spelling when the spelling isn't in the code, is frustrating and time wasting. It's also takes alot more time for me to look up every line of code and cut/paste it in, rather than, in some cases, answer from memory...(depends on situation)...

    ... which is why I recommend to post a short, self-contained program that shows the behaviour without needing any external setup instead of only explaining in prose a summary in which key parts are neccessarily missing (because if they weren't missing, you'd know the solution already). Of course, this is still time consuming for you, but as it's your problem, I find it fitting that you spend your time and effort on it instead of requiring others to do so.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://985098]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (10)
As of 2014-12-18 03:31 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (41 votes), past polls