On Wed, Sep 26, 2012 at 9:59 PM, Anthony Liguori wrote:
> Alex Williamson writes:
>
>> When creating structure names in CamelCase, it's easy to have
>> back-to-back capitals when using acronyms (ex. PCIINTxRoutingNotifier,
>> QEMUSGList, VFIOINTx). In the worst case these can look like macros,
>
On Wed, 2012-09-26 at 16:59 -0500, Anthony Liguori wrote:
> Alex Williamson writes:
>
> > When creating structure names in CamelCase, it's easy to have
> > back-to-back capitals when using acronyms (ex. PCIINTxRoutingNotifier,
> > QEMUSGList, VFIOINTx). In the worst case these can look like macr
Alex Williamson writes:
> When creating structure names in CamelCase, it's easy to have
> back-to-back capitals when using acronyms (ex. PCIINTxRoutingNotifier,
> QEMUSGList, VFIOINTx). In the worst case these can look like macros,
> but even adjoining a single, all-caps acronym makes it more di
On Mon, 2012-09-24 at 22:01 +0200, Michael S. Tsirkin wrote:
> On Mon, Sep 24, 2012 at 12:08:16PM -0600, Alex Williamson wrote:
> > When creating structure names in CamelCase, it's easy to have
> > back-to-back capitals when using acronyms (ex. PCIINTxRoutingNotifier,
> > QEMUSGList, VFIOINTx). In
On Mon, Sep 24, 2012 at 12:08:16PM -0600, Alex Williamson wrote:
> When creating structure names in CamelCase, it's easy to have
> back-to-back capitals when using acronyms (ex. PCIINTxRoutingNotifier,
> QEMUSGList, VFIOINTx). In the worst case these can look like macros,
> but even adjoining a si
When creating structure names in CamelCase, it's easy to have
back-to-back capitals when using acronyms (ex. PCIINTxRoutingNotifier,
QEMUSGList, VFIOINTx). In the worst case these can look like macros,
but even adjoining a single, all-caps acronym makes it more difficult
to interpret. For example
