Stories
Slash Boxes
Comments

SoylentNews is people

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Insightful) by Ethanol-fueled on Saturday May 26 2018, @12:16AM (3 children)

    by Ethanol-fueled (2792) on Saturday May 26 2018, @12:16AM (#684276) Homepage

    Do what I do to fix bugs - wrap everything in a giant try block followed by an empty catch block. Your program will continue working like a charm, if your customer doesn't care which places the decimal points go in his payroll system.

    Starting Score:    1  point
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Sunday May 27 2018, @01:17AM

    by Anonymous Coward on Sunday May 27 2018, @01:17AM (#684717)

    I have no words.

    Yes. I do. Don't do this in powershell. Try doesn't always catch clean which can result in broken program.

  • (Score: 0) by Anonymous Coward on Wednesday May 30 2018, @10:05PM

    by Anonymous Coward on Wednesday May 30 2018, @10:05PM (#686511)

    I don't know if you are serious, and I hope you aren't.

    But, I am sad to say I have seen this behavior in legacy code my team has had to maintain. When I asked devs who had been here a long time why there were so many empty catch blocks in the code, they said former management wanted to reduce the amount of errors the service produced, and gave a ridiculous timeframe to get the work done. The only solution was to remove the logging statements in the catch blocks. This is a true story. :(

  • (Score: 0) by Anonymous Coward on Sunday June 10 2018, @01:44AM

    by Anonymous Coward on Sunday June 10 2018, @01:44AM (#690999)

    Please don't work on anything important in the real world.