???

Pascal Bourguignon a écrit :

Aie, mal aux yeux de lire ca.

6.2.5 Types

6.2.5-20
- An array type describes a contiguously allocated nonempty set of
objects with a
particular member object type, called the element type.36) Array types
are
characterized by their element type and by the number of elements in
the array. An
array type is said to be derived from its element type, and if its
element type is T, the
array type is sometimes called ''array of T''. The construction
of an array type from
an element type is called ''array type derivation''.

Dans l'article <45907404$1_1@news.bluewin.ch>,
Yves Lange écrit:

int main (void)

Peut-être un \n à la fin des chaîne dans les printf.
Maintenant, tu devrais obtenir

B != A

Hi,

As many, I'm looking for a more efficient use of the C preprocessor.
The gcc manual specifies:

"The macro's body ends at the end of the `#define' line. You may
continue the definition onto multiple lines, if necessary, using
backslash-newline. When the macro is expanded, however, it will all
come out on one line. For example,

#define NUMBERS 1, \
2, \
3
int x[] = { NUMBERS };
==> int x[] = { 1, 2, 3 };

The most common visible consequence of this is surprising line numbers
in error messages.

There is no restriction on what can go in a macro body provided it
decomposes into valid preprocessing tokens. Parentheses need not
balance, and the body need not resemble valid C code. (If it does not,
you may get error messages from the C compiler when you use the macro.)
"