<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - compiler padding causes reply parsing to use incorrect offsets"
href="https://bugs.freedesktop.org/show_bug.cgi?id=23403#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - compiler padding causes reply parsing to use incorrect offsets"
href="https://bugs.freedesktop.org/show_bug.cgi?id=23403">bug 23403</a>
from <span class="vcard"><a class="email" href="mailto:peter.harris@hummingbird.com" title="Peter Harris <peter.harris@hummingbird.com>"> <span class="fn">Peter Harris</span></a>
</span></b>
<pre>In general, I am opposed to language-specific cruft in the protocol
description.
If I may make a suggestion, all structs/requests/replies/etc should be treated
as packed. Instead of adding a "packed" attribute, explicit padding should be
added to the few remaining objects that currently contain implicit padding.
c_client.py (and/or xtypes.py) could then be enhanced to automatically notice
structs that don't fit the default C alignment rules and add whichever
annotations the C compiler needs.
What do you think?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>