docs/devel/style.rst

91 Lines should be 80 characters; try not to make them longer.
118 names and function type names should also be in CamelCase.  Scalar type
140 that are widely called from across the codebase should not have any
146 However, if there is an obvious subsystem-specific prefix it should be
206 blocks) are generally not allowed; declarations should be at the beginning
247 Multiline comment blocks should have a row of stars on the left,
303 Headers should normally include everything they need beyond osdep.h.
316 harder. You should consider carefully if the same effect can be
320 If you do use template header files they should be named with the
327 It should be common sense to use the right type, but we have collected
334 If a variable is counting something, it should be declared with an
337 If it's host memory-size related, size_t should be a good choice (use
367 it may be 32 or 64 bits depending on which target is being built. It should
408 "snake_case").  Each named struct type should have a CamelCase name and a
411 Since certain C compilers choke on duplicated typedefs, you should avoid
442 Underscore capital, double underscore, and underscore 't' suffixes should be
461 Care should be taken to avoid introducing places where the guest could
466 fall-back to a smaller one if need be we should use functions like
525 so instead of e.g. isalnum you should use qemu_isalnum.
544 C code in QEMU should be written to the C11 language specification. A
552 produce better code).  In general, code in QEMU should follow the language
666 structure should always be the parent and leave a visual space between
671 For a storage structure the first declaration should always be called
672 "parent_obj" and for a class structure the first member should always
801 monitor commands should never exit().
805 translation or device emulation).  Guests should not be able to
851 and '%#...'. For consistency the only one way should be used. Arguments for