stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Black (JIRA)" <>
Subject [jira] Commented: (STDCXX-261) runall should parse tests and examples in the same manner
Date Thu, 03 Aug 2006 16:54:14 GMT
    [ ] 
Andrew Black commented on STDCXX-261:

The main drawback I can see with using RCS comments is that we would need to reimplement the
ident utility in some manner to retrieve the RCS comments strings.  ident isn't a part of
the POSIX spec, and even if it were, it would be necessary to provide an implementation for

A couple minor concerns would be ensuring that the RCS comment strings aren't optimized away
and that RCS comments are inserted into the shell script (locale) targets.

To me, useful information that could be embedded would be the location of the reference input
file (if one exists) and the reference output file.  This would eliminate the search logic
used at this time to locate said files.  This would also allow tests to have such files. 
Another piece of useful information could be the format of the output file generated, allowing
us to distinguish test suite driver output from compatibility layer output (eliminating the
compat global and the --compat/--nocompat switches).

In an off-line discussion with Martin, he noted that another useful piece of information that
could be embedded in a test would be platform-specific control over which tests are enabled/disabled.
 I wonder whether it would make more sense for such enable/disable logic to reside in the
test suite/test driver, rather than the exec utility.

> runall should parse tests and examples in the same manner
> ---------------------------------------------------------
>                 Key: STDCXX-261
>                 URL:
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Andrew Black
>            Priority: Minor
> At this time, several of the self tests (0.cmdopts.out, 0.printf.out, 0.strncmp.out,
0.valcmp.out) produce output that lacks a summary section.
> The (or runall.c) utility should be able to compare the output of these tests
against a reference file in the same manner that the output is compared for examples.
> An extension of this concept is that it might make sense to unify the logic used to check
the test and example results, so that the same process would be used for both tests and examples.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message