|Subject:||Re: [Qemu-devel] Coding style, C++ compatible code (was Re: [Qemu-devel] [PATCH 02/22] eepro100: cast a void * makes no sense)|
|Date:||Wed, 26 Aug 2009 09:58:45 -0700|
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.
An old platitude says it best; Slovenly writing indulges the writer while clear writing indulges the reader.
|[Prev in Thread]||Current Thread||[Next in Thread]|