|| && ? | & _ == != = << >> <= >= < > + - % ! ~

This means that white space need not follow or precede identifiers or numbers if preceded or followed by one of these tokens. (The IDL specification requires white space, as in 'a = b + 3', instead of allowing 'a=b+3'.) This also seems to be the behavior of the OSF DCE IDL compiler.

long *op(void);

nor does it allow for structure or union returns. While this could be considered correct (everything could be hidden in a defined type), the DCE IDL compiler and, of course, C compiler allow a much richer operation return. The supported grammar will be the following.

[operation_attributes] <type_spec> <declarator>

where <declarator> must contain a <function_declarator>. (If a <function_declarator> does not exist, then a variable is declared, which results in an error.) Declaring an array of operations or an operation returning an array (both allowed by this grammar) will be detected and flagged as an error.

• A transmitted type used in [transmit_as()] cannot have the [represent_as] attribute.

• A union arm may not be or contain a [ref] pointer.

• If a conformant and/or varying array appears in a structure, the array size attribute variable may not be a pointer (that is, it must be a non-pointer, integer element within the structure).

const char *str = "abc" "def";

is treated the same as

const char *str = "abcdef";

const char *str = "abc\
 def";

is treated the same as

const char *str = "abcdef";