Re: Coding style, C++ compatible code (was Re: [Qemu-devel] [PATCH 02/22] eepro100: cast a void * makes no sense)

[malc]

On Thu, 27 Aug 2009, M?ns Rullg?rd wrote:

> Kent Harris <address@hidden> writes:
> 
> > Stefan,
> >
> > I'm with you 100 percent.  I already complained to this group a couple
> > of months ago about the void* casting issue (and also using "private"
> > as a structure element name as that barfs C++ as well -- there are
> > others.)
> >
> > For my situation, these problems within C-language source files are
> > not an issue but when they occur inside a QEMU header file that I must
> > include from my C++ device models, my compilations fail.
> > Consequently, I have a whole series of patch files to the QEMU source
> > that I have to apply to correct these (trivial) coding errors.  Each
> > time a new QEMU release comes out, I have to recreate the patch
> > files.  Frustrating to say the least.
> 
> I have a great idea.  For maximum portability, lets all start writing
> code like this: http://ideology.com.au/polyglot/polyglot.txt That way,
> it will work in almost any language, and everybody will be happy.

Reminds me of http://fly.srk.fer.hr/ioccc/1986/applin.c

-- 
mailto:address@hidden