" Missing ';' before 'type' " ?

Code:

---

                switch(LOWORD(wParam))
                {
                        case ID_FILE_EXIT:
                                PostMessage(mainww, WM_CLOSE, 0, 0);
                        break;
                       
                        case ID_HELP_ABOUT:
/*error here */                        int ret = DialogBox(GetModuleHandle(NULL), MAKEINTRESOURCE(ID_ABOUT), mainww, AboutDlgProc);
                        break;
                }

---

what's wrong? I have all my semicolons!

change

Code:

---

int ret =

---

to

Code:

---

ret =

---

Is that the only error that you're getting?

you cannot declare variables in a switch!

to get around this limitation you can use blocking,

Code:

---

case ID_HELP_about :
{
    int ret = DialogBox(GetModuleHandle(NULL), MAKEINTRESOURCE(ID_ABOUT), mainww, AboutDlgProc);
}
break;

---

That code stills has you declaring a variable inside the switch no-one

I'm getting off the original question here a little, but...

>you cannot declare variables in a switch!

Yes you can. But the usefulness may be questionable. Here is a hideous example (for entertainment mostly).

Code:

---

#include <stdio.h>

int main(void)
{
  int i;
  for ( i = 0; i < 5; ++i )
  {
      switch ( i )
      {
        int i = 42; /* 'i' is declared, but not initialized,
                        it also hides the outer 'i' */
      case 0: i = printf("Hello\n"); goto hell;
      case 1: i = printf("everybody!\n"); goto hell;
      default: hell: printf("i = %d\n", i++);
      }
  }
  return 0;
}

/* my output
Hello
i = 6
everybody!
i = 11
i = 12
i = 13
i = 14
*/

---

>That code stills has you declaring a variable inside the switch no-one

note: that what i said was a method of "By-passing" this, by using the blocking functionality.

>Yes you can. But the usefulness may be questionable. Here is a hideous example (for entertainment mostly).

Well, to be honest i've actual never seen that one... and i'm not sure as to how legal that is... anyway both ways are technically loop-holes, ie abuses of the blocking operators, and both should be avoided, where possible.