JoshuaAshton

I find it more amusing you don't see the blatant circular logic flaw in that.

So you should be required to go through a government licensing programme to be able to tell the government they fucked up? :D

b sqr 4 a c * * - sqrt

Yeah no. This being "bug free" seems like a joke.

Rasengan goes 1 week without spamming his inane crap on HN challenge!

Fucking sellouts.

I wonder when Rasengan will realize how much he messed up.

Or you can just select to hold that package for updates in a package manager in a competent distro that actually gets needed security and usability updates.

Doesn't help that some ""stable"" packages are outright broken and won't be fixed until the next release (ie. MinGW is stuck on a broken version of 8.3 which has a buttload of compiler bugs I keep hitting)

The default idea behind exceptions is silly and as I stated before, they typically get generated to some horrific code

Usually documentation tends to have this, or you can look at the function and immediately know what it will return, whereas with exceptions any passthrough errors are transparent.

> You also can't possibly know all error codes to handle for a function if it calls other functions returning error codes

You aren't using error codes or documenting correctly. You get a choice whether the error propogates upstream