1,716 reputation
31939
bio website
location Singapore
age
visits member for 4 years
seen yesterday


1d
revised Why have many programmers moved to using exception handling for input or output?
added 96 characters in body
May
18
revised Is initializing a char[] with a string literal bad practice?
clarify "treuss"
May
18
suggested approved edit on Is initializing a char[] with a string literal bad practice?
May
14
comment Is it good practice to rely on headers being included transitively?
@DocBrown, #pragma once settles it, no?
May
1
comment Are my negative internship experiences representative of the real world?
@JarrodRoberson, Doesn't "Software systems degenerate and rot because of maintenance, not because of the lack of it, A system that is in place for years with no code changes by definition meets all its requirements and goals and is a success" contradicts Jargon Files' definition: "degradation of a software program over time even if nothing has changed"?
Apr
30
awarded  Yearling
Apr
30
comment How to convince my boss that quality is a good thing to have in code?
@GaretClaborn, The place is small (4 people?) so it's easy to win the battle. In many places, leaving is a better solution.
Apr
29
revised What limitation will we face if each user-perceived character is assigned to one codepoint?
added 75 characters in body
Apr
29
revised What limitation will we face if each user-perceived character is assigned to one codepoint?
deleted 13 characters in body; edited title
Apr
29
revised What limitation will we face if each user-perceived character is assigned to one codepoint?
deleted 13 characters in body; edited title
Apr
25
comment Why have many programmers moved to using exception handling for input or output?
...................................point "programming languages designed in the last 25 years use Exceptions as their main (if not only) error handling mechanism" ipso facto provides 0 reasoning to the judgement of exceptions vs ercodes. Indeed, Joel's article is exactly talking about these languages C# and Java, exceptions give 1) abrupt jump 2) too many exit points.
Apr
25
comment Why have many programmers moved to using exception handling for input or output?
@AK_, If you are going to comment on an answer and say it's wrong, you will provide at least 1 reason why it's wrong. I see zero. Failing to provide any reasons renders your comment empty in content. I see many words from you but no reasoned points made. First thing first, programming languages aren't perfect, the.............................................................................‌​‌​................................
Apr
25
comment Why have many programmers moved to using exception handling for input or output?
................................................................... concept of exceptions vs ercode-based handling. You can do that with either method. Regarding "operating at a far lower level than most code should care about", note that we are not comparing low level code with high level code. We're comparing exceptions vs error-handling in situations where both are available. The flaws of exceptions (the 2 points above) applies to both low level and high level code. The only difference between low level and high level is reliability: whether failure has consequences or not.
Apr
25
comment Why have many programmers moved to using exception handling for input or output?
@DougM, The explanation is so clear and straightforward that if you're asking what the reasons are, I sincerely doubt you had read them. I'll summarize the article: It's due to 1) abrupt jump 2) too many exit points. Regarding "probably WANT a taskbar icon to show its square, even if the icon it was looking for couldn't be shown", That's orthogonal to the ........................................................................
Apr
25
revised Why have many programmers moved to using exception handling for input or output?
edited body
Apr
24
revised Why have many programmers moved to using exception handling for input or output?
edited body
Apr
24
comment Why have many programmers moved to using exception handling for input or output?
"Because input and output are unreliable" does not explain why exceptions are used instead of error-codes. As such, I believe I have a better explanation (despite the -15 downvotes) at programmers.stackexchange.com/a/279911/24257 .
Apr
24
comment Why have many programmers moved to using exception handling for input or output?
@utnapistim, This is an unbalanced comparison. If you wish to weigh the use case whereby we have multiple error codes, you must weigh it against the equivalent use case whereby we have multiple exception paths, as can be seen in the long snippet in stackoverflow.com/a/315967/632951 . If you are going to weigh the "catch-all" — } catch(e) { /* handle all */ } , then you must weigh it against the two-state errorcode 0 and 1 which doesn't use switch.
Apr
24
comment Why have many programmers moved to using exception handling for input or output?
.............................. answer only when the reasoning is flawed, not just because it happens to be on the minority side (goodness -15 votes?) of a religious flame-topic.
Apr
24
comment Why have many programmers moved to using exception handling for input or output?
@AK_, While that's irrelevant, I really doubt he'll not stand behind it today. His post on AMA shows I'm on the right track. Also, the links I've posted provides strong reasoning that exception-based code has many pitfalls. If you've skipped through all of them, you can start from Raymond Chen's reasoned blogpost 6 paragraphs before "it is extraordinarily difficult to see the difference between bad exception-based code and not-bad exception-based code". I'll delete the ...........................................