>> Yeah, that's wrong. I'll fix it. I suspected it was wrong, but it compiled >> fine. > > perhaps clang should also detect and refuse such constructs in the future ;). bug number? :-) Cheers, Rafael