+ Todd Sabin <[EMAIL PROTECTED]>: | Technically, the only thing that's non-conformant is your code. | You're invoking undefined behavior by passing something that's not a | type specifier, so implementations can do anything they want.
Doesn't the specification always say so explicitly when something invokes undefined behaviour? It doesn't in this case. - Harald
