well, yea... an if statement would suffice, but it's making calls to another subroutine, if something in that subroutine returns a value, but there's a separate error (aside from the return value)...
Type: Posts; User: X_e_e_k
well, yea... an if statement would suffice, but it's making calls to another subroutine, if something in that subroutine returns a value, but there's a separate error (aside from the return value)...
yea that empty string was just an example for something on a bigger scale, i'm starting to get the drift of how it affects the flow of code...
are you guys thinking about program runtime error...
here's my take on it, but i don't know if i'm right
int ex; //some global variable
int routine1() {
int reply = routine2();
if (ex) {
// handle the exception
}
}
/* would be like this...
I'm porting some code of a game I found on the web to C. It was written in Visual Basic 2005.
It goes a little something like..
Try
Do
'code block
Loop Until Not Change
Catch ex...