??? 09/28/05 13:52 Read: times |
#101662 - who cares if an exceptiom is "acceptable Responding to: ???'s previous message |
might be an acceptable exception
who cares if an exceptiom is "acceptable", if it happens, you need to take care of it regardless. if it was adequately documented in the function description. In my experience it's unusual for the function name to accurately describe such complicated behaviour and doesn't end up being called 'char getCharFromBufExceptCRThrowsException();'. In so called "real C" (oh, how I hate that expression) you have mile long function names that it takes about 1/2 hour to get spelled right for every function call you invoke and since C is self documenting you have no comments. In "real programs" you have short function names and the functions behaviour is described in the function header - oops, that would be comments, would it not. So, why a crummy name that will be misspelled for every use, why not just FetchBufChar and a complete understandable function header. Erik |
Topic | Author | Date |
RET to a different address | 01/01/70 00:00 | |
here is how pseudocode | 01/01/70 00:00 | |
RET to a different address | 01/01/70 00:00 | |
no flaw, but 1.000.000 gotchas | 01/01/70 00:00 | |
That's what I wanted to know | 01/01/70 00:00 | |
Yes | 01/01/70 00:00 | |
"clever" | 01/01/70 00:00 | |
OT: my wife | 01/01/70 00:00 | |
no flaw, but seriously not recommended | 01/01/70 00:00 | |
experience | 01/01/70 00:00 | |
reload SP | 01/01/70 00:00 | |
restoring stack | 01/01/70 00:00 | |
Recognisable string![]() | 01/01/70 00:00 | |
named return value | 01/01/70 00:00 | |
Bad Practice | 01/01/70 00:00 | |
Well phrased | 01/01/70 00:00 | |
What I am doing with it | 01/01/70 00:00 | |
try...catch | 01/01/70 00:00 | |
setjmp / longjmp | 01/01/70 00:00 | |
when to try ... catch | 01/01/70 00:00 | |
the borderline | 01/01/70 00:00 | |
Promises | 01/01/70 00:00 | |
who cares if an exceptiom is "acceptable | 01/01/70 00:00 | |
Parsing input data | 01/01/70 00:00 |