Eric Blake wrote:
> According to Eric Blake on 12/23/2009 2:45 PM:
>>> Possibility 1: Put the SIGNATURE_CHECK into a file tests/signature.h, and
>>> put
>>> ASSERT, SIZEOF and a few others into tests/macros.h. A test looks like this:
>>>
>>
>> It's less work for me if we go with possibility 2, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 12/23/2009 2:45 PM:
>> Possibility 1: Put the SIGNATURE_CHECK into a file tests/signature.h, and put
>> ASSERT, SIZEOF and a few others into tests/macros.h. A test looks like this:
>>
>
> It's less work for me if we go with
Bruno Haible clisp.org> writes:
> So, how to resolve this contradicting requirements?
>
> Possibility 1: Put the SIGNATURE_CHECK into a file tests/signature.h, and put
> ASSERT, SIZEOF and a few others into tests/macros.h. A test looks like this:
>
>#include
>
>#include
>
>#incl
Hi Eric,
> that also means that test/macros.h must NOT include any system headers (so
> that
> SIGNATURE_CHECK can be invoked after config.h, macros.h, and exactly one
> system
> header has been included).
Thanks for stating this so clearly. Because on the other hand, I would like
tests/macros
