• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 991 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Return Statements inside Case Statements

Justin McCurdy

I encountered a wierd runtime error after compiling and running the following statement:

FuncCall(unsigned char casenum)
{
  switch (casenum)
  {
    case 0x00:
        return 0x0100;
    default:
        return 0x1000;
  }
}

This code compiled with no errors or warnings as part of a much larger chunk of code. When run, this code caused the service watchdog timer to reset the module every time it encountered the statement:

U16 GetReturn;
GetReturn = FuncCall(x);


I then replaced the above code with:

FuncCall(unsigned char casenum)
{
  switch (casenum)
  {
    case 0x00:
        return (0x0100);
    default:
        return (0x1000);
  }
}

and it worked perfect the first time. The only changes to the code consisted of perenthesis changes as listed above. Is there some rule that states constants need to be returned in perenthesis while variables can be returned without them, or have I just encountered a compiler issue? Any ideas?

Parents
  • 0

    You didn't specify the return type of the function, yet "code compiled with no errors or warnings". Shouldn't it have given "warning C35: 'FuncCall': uses old-style declarator" ?
    Anyway, if you have doubts about the code generated by the compiler, why not check the disassembly?

    - mike

Reply
  • 0

    You didn't specify the return type of the function, yet "code compiled with no errors or warnings". Shouldn't it have given "warning C35: 'FuncCall': uses old-style declarator" ?
    Anyway, if you have doubts about the code generated by the compiler, why not check the disassembly?

    - mike

Children
No data