qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: "Måns Rullgård" <mans@mansr.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Coding style, C++ compatible code (was Re: [Qemu-devel] [PATCH 02/22] eepro100: cast a void * makes no sense)
Date: Thu, 27 Aug 2009 13:39:34 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.64.0908271339190.2270@linmac.oyster.ru> (raw)
In-Reply-To: <yw1xskfejhza.fsf@unicorn.mansr.com>

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

> Kent Harris <ksh@vine.com> 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:av1474@comtv.ru

  reply	other threads:[~2009-08-27  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 16:58 [Qemu-devel] Coding style, C++ compatible code (was Re: [Qemu-devel] [PATCH 02/22] eepro100: cast a void * makes no sense) Kent Harris
2009-08-26 23:00 ` Måns Rullgård
2009-08-26 23:03 ` Måns Rullgård
2009-08-27  9:39   ` malc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-24 11:03 [Qemu-devel] [PATCH 00/22] Indirection Cleanup Juan Quintela
2009-08-24 11:03 ` [Qemu-devel] [PATCH 02/22] eepro100: cast a void * makes no sense Juan Quintela
2009-08-24 12:56   ` Stefan Weil
2009-08-24 13:51     ` Markus Armbruster
2009-08-26 13:52       ` [Qemu-devel] Coding style, C++ compatible code (was Re: [Qemu-devel] [PATCH 02/22] eepro100: cast a void * makes no sense) Stefan Weil
2009-08-26 15:20         ` Måns Rullgård
2009-08-26 15:58           ` Reimar Döffinger
2009-08-26 16:08             ` Avi Kivity
2009-09-03 12:05               ` Stuart Brady

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0908271339190.2270@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=mans@mansr.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).