va_arg()



Hello,

I have a question about va_arg() usage :
Is there any way how I can check or ensure at compile time that
va_arg() is not called when there are
no next arguments anymore.
I understood that calling va_arg() when there are no next arguments
causes an undefined behaviour.

Thanks

.



Relevant Pages

  • Re: "issue" meaning "problem"
    ... This usage is long familiar in N.America and probably Britain ... Much of my work these days is in engineering design. ... end product does not work as intended, then there is a fault somewhere ... Calling it an issue is ...
    (alt.usage.english)
  • Re: "issue" meaning "problem"
    ... This usage is long familiar in N.America and probably Britain as ... Much of my work these days is in engineering design. ... Calling it a fault ...
    (alt.usage.english)
  • Re: "issue" meaning "problem"
    ... This usage is long familiar in N.America and probably Britain as ... Much of my work these days is in engineering design. ... Calling it a fault ...
    (alt.usage.english)
  • Re: crash the application at calling API function as GetCursorInfo...
    ... I am not usage typedefing the CURSORINFO struct only illustration. ... But whether usage alignment. ... >> calling next this function. ... >> with a function pointer declared with a different calling convention. ...
    (microsoft.public.win32.programmer.gdi)
  • Re: question on const
    ... >> Are you trying to say that all possible undefined behaviour ... int main ... Yet very few systems will complain at run-time whether or not UB ... and none that I know of will complain at compile time. ...
    (comp.lang.c)