Re: [cc65] Compiler: Should xvsnprintf() work?

Hi,

Am 23.03.2013 23:39, schrieb Ullrich von Bassewitz:
> Since you're not getting the error from 3., and you're not using one of the
> compilers from 2., only 1. can be true. And if this doesn't work, then the
> va_copy that comes with your compiler must be broken.

sorry for the noise, but just one big bell rang. When I first tried to 
port the compiler to MSVC10 (4 weeks ago), I got the 'no va_copy' 
message and fixed that by copying the WATCOM defintion without thinking 
about it further. Continuing today without that in mind doesn't seem to 
be a good idea.

I've added now:

#if defined(_MSC_VER)
#define va_copy(dest, src)  dest = src
#endif

which does the correct job.

Just learned three things:
1. MSVC is one more time away from the standard.
2. Interrupting a task can be even more worse than you think.
3. Some retired maintainers may provide a much better support than even 
no retired ones!

Thank you very much!

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.