Diego Novillo <dnovi...@google.com> writes:
> On Mon, Oct 15, 2012 at 11:55 AM, Ian Lance Taylor <i...@google.com> wrote:
>
>> In my opinion, supporting the full range of GCC testsuite annotations
>> means imposing a lot of mechanism that the Go testsuite does not
>> require. It would complicate the Go testsuite for no benefit.
>> Anybody who can understand the GCC testsuite annotations can
>> understand the much simpler Go testsuite annotations.
>
> Agreed. The fact that we have to suffer DejaGNU does not gives the
> right to make other projects miserable.
But importing different upstream testsuites with different annotation
systems allows them to make GCC maintainer's lives miserable? If this
trend continues, maintainers need to cope with several different
annoation systems with different capabilites instead of a single one,
some of them lacking necessary features which are already present in
DejaGnu (which leads to handling stuff that's just a simple annotation
in DejaGnu in the testsuite drivers instead). I'm not asking upstreams
to deal with DejaGnu themselves, just to accept that the dg annotations
live in their repos.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
