<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Assuming you're writing a "book", I hope you meant "concise".</blockquote>
<div><br><br>Yes, it will be concise about Pyrex, so I could set this aside (but as it is mentioned when talking about importing a Python type like complex, I thought about telling everything about this syntax).<br> </div>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Giving good<br>examples means leaving out everything that is not necessary to avoid confusion
<br>or mental divergence. So, if you're not writing specifically about how to make<br>types public and how to export them to external code, you should not use the<br>syntax you mentioned in your book.</blockquote><div>
<br><br>Yes, you're probably right. Usually, people won't use this. I'll think about it.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The names given the "cdef public ... [ object NAME, type NAME ]" syntax allow<br>Pyrex to export the internally mangled names as readable, user-defined names<br>in a header file to make them available to external code. That's almost all
<br>there is to it.</blockquote></div><br>OK, so it is a very narrow field of application.<br><br>Thank you for the explanation.<br><br>Matthieu<br>