46 lines · c
1/* RUN: %clang_cc1 -std=c89 -fsyntax-only -pedantic -verify %s2 RUN: %clang_cc1 -std=c99 -fsyntax-only -pedantic -verify %s3 RUN: %clang_cc1 -std=c11 -fsyntax-only -pedantic -verify %s4 RUN: %clang_cc1 -std=c17 -fsyntax-only -pedantic -verify %s5 RUN: %clang_cc1 -std=c2x -fsyntax-only -pedantic -verify %s6 */7 8/* WG14 DR157: yes9 * Legitimacy of type synonyms10 *11 * Part 1 is about whether you can use a typedef to void in place of void in12 * a function parameter list and still get a function with a prototype that13 * accepts no arguments. You can.14 *15 * Part 2 is about whether you can use a typedef to int in place of int in16 * the declaration of main(). You can.17 *18 * Part 3 is about whether there are situations where a typedef cannot be used19 * in place of a type name.20 */21typedef void dr157_1_t;22extern int dr157(dr157_1_t); /* ok */23int dr157(dr157_1_t) { /* ok */24 /* You cannot combine a typedef with another type specifier. */25 typedef int Int; /* expected-note {{previous definition is here}} */26 long Int val; /* expected-error {{redefinition of 'Int' as different kind of symbol}}27 expected-error {{expected ';' at end of declaration}}28 */29 30 return 0;31}32 33typedef int dr157_2_t;34dr157_2_t main(void) { /* Still a valid declaration of main() */35}36 37/* A function definition cannot use a typedef for the type. */38typedef void dr157_3_t(void);39extern dr157_3_t dr157_2 { /* expected-error {{expected ';' after top level declarator}} */40}41 42/* FIXME: all diagnostics that happen after the previous one about expecting a43 * a ';' are silenced, so this test needs to be in its own file to prevent44 * accidentally incorrect testing.45 */46