Intel Mac and YES (or NO)

After having worked on my faithful G4 Powerbook for the last 2 years, I finally got a beautiful fast brand new Intel Mac from my work this week. YES!

First thing I did was to test VisDoc. The latest bug reports I got were all from people using Intel Macs, so I was getting suspicious there might be something platform related. To my dismay I found out my users had been right. And the output very wrong.

Something peculiar goes on in Intel's internals. A simple function like

- (BOOL)isConst
{
   return [mType containsObject:@"const"];
}

should return a BOOL, right? Apparently not anymore, because [inMember isConst] now happily returns a pointer and that is never a NO or 0. To get reliable results I need to cast every boolean return value to BOOL: (BOOL)[inMember isConst]. Redundant but it does the job.

VisDoc 2.0.1 should fix all outstanding bugs for Mac Intel computers.