On Thu, Nov 5, 2009 at 10:35 PM, David Cournapeau <
[email protected]> wrote:
> Charles R Harris wrote:
> > So you are going to leave us all hanging here in curiosity? What is
> > your solution?
>
> I had to sleep :)
>
> The solution is based on parsing the generated binary code - that's how
> MPFR is doing it, so it has been tested in the wild. The code to compile
> is something like:
>
> /* "before" is 16 bytes to ensure there's no padding between it and "x".
> * We're not expecting any "long double" bigger than 16 bytes or with
> * alignment requirements stricter than 16 bytes. */
> typedef long double test_type;
>
> struct {
> char before[16];
> test_type x;
> char after[8];
> } foo = {
> { '\0', '\0', '\0', '\0', '\0', '\0', '\0', '\0',
> '\001', '\043', '\105', '\147', '\211', '\253', '\315', '\357' },
> -123456789.0,
> { '\376', '\334', '\272', '\230', '\166', '\124', '\062', '\020' }
> };
>
> They compile it, parse with awk from the dump od -f.
>
So the before/after bits are tags that mark the beginning/end of the type
for the parse? Any particular reason not to use a string? "David Cournapeau"
should work :-)
Chuck
_______________________________________________
NumPy-Discussion mailing list
[email protected]
http://mail.scipy.org/mailman/listinfo/numpy-discussion
