* Returns: ---
*
* Use: Formats a report about the benchmark performance. This
- * function is intended to be called on by an output
- * @ebench@ function.
+ * function is intended to be called on by an output @ebench@
+ * function.
*/
extern void tvec_benchreport
extern PRINTF_LIKE(2, 3)
void tvec_notice(struct tvec_state */*tv*/, const char */*msg*/, ...);
-/* --- @tvec_unkreg@ --- *
+/* --- @tvec_unkregerr@ --- *
*
* Arguments: @struct tvec_state *tv@ = test-vector state
* @const char *name@ = register or pseudoregister name
* unrecognized.
*/
-extern int tvec_unkreg(struct tvec_state */*tv*/, const char */*name*/);
+extern int tvec_unkregerr(struct tvec_state */*tv*/, const char */*name*/);
-/* --- @tvec_dupreg@ --- *
+/* --- @tvec_dupregerr@ --- *
*
* Arguments: @struct tvec_state *tv@ = test-vector state
* @const char *name@ = register or pseudoregister name
* assigned already in the current test.
*/
-extern int tvec_dupreg(struct tvec_state */*tv*/, const char */*name*/);
+extern int tvec_dupregerr(struct tvec_state */*tv*/, const char */*name*/);
/* --- @tvec_humanoutput@ --- *
*
* (`Test Anything Protocol') format.
*
* TAP comes from the Perl community, but has spread rather
- * further. This driver produces TAP version 14, but pretends
- * to be version 13. The driver produces a TAP `test point' --
- * i.e., a result reported as `ok' or `not ok' -- for each input
- * test group. Failure reports and register dumps are produced
- * as diagnostic messages before the final group result. (TAP
- * permits structuerd YAML data after the test-point result,
- * which could be used to report details, but (a) postponing the
- * details until after the report is inconvenient, and (b) there
- * is no standardization for the YAML anyway, so in practice
- * it's no more useful than the unstructured diagnostics.
+ * further. This driver currently produces TAP version 14, but
+ * pretends to be version 13. The driver produces a TAP `test
+ * point' -- i.e., a result reported as `ok' or `not ok' -- for
+ * each input test group. Failure reports and register dumps
+ * are produced as diagnostic messages before the final group
+ * result. (TAP permits structuerd YAML data after the
+ * test-point result, which could be used to report details, but
+ * (a) postponing the details until after the report is
+ * inconvenient, and (b) there is no standardization for the
+ * YAML anyway, so in practice it's no more useful than the
+ * unstructured diagnostics.
*/
extern struct tvec_output *tvec_tapoutput(FILE */*fp*/);