Live data from Hacker News

Some of the error messages produced by Apple's MPW C compiler (2006)

cs.cmu.edu

21–30 of 46 posts

Re: Some of the error messages produced by Apple's MPW C compiler (2006)

#22
post #14

Just for some context, the MPW C compiler that produced those messages was actually not developed internally at Apple, but was rather done by Green Hills Software [1] under contract as mentioned on the wikipedia page [2] and its source [3] which is funnily enough about this exact same topic. [1] https://en.m.wikipedia.org/wiki/Green_Hills_Software [2] https://en.m.wikipedia.org/wiki/Macintosh_Programmer%27s_Wor... [3…

I forget why I went into their building, but I always remember a giant T-rex skull in their entryway. I'm not making this up, am I?

I did find this press release, but it really just raises more questions than answers anything. https://www.prnewswire.com/news-releases/ubm-electronics-and...

Re: Some of the error messages produced by Apple's MPW C compiler (2006)

#25
post #10
post #3

Is anyone at Apple allowed to have a sense of humor anymore?

Their test OS for iPhone's is hilarious https://www.theiphonewiki.com/wiki/TigrisAni_15A93720r

You must be a hoot at comedy clubs on amateur night. I don't see anything remotely funny about anything in that link.

Re: Some of the error messages produced by Apple's MPW C compiler (2006)

#28

> This label is the target of a goto from outside of the block containing this label AND this block has an automatic variable with an initializer I get this issue a lot on modern compilers, when trying to write switch/macro-based coroutines ( https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html ) in C++. Does anyone have a workaround? (I hope it doesn't involve C++20 coroutines... I still don't understand the…

If your variable is a class without a trivial default constructor, then you're out of luck. Otherwise, the workaround is to not initialize the variable, and to instead assign to it immediately after declaring it (e.g., replace "int x = 42;" with "int x; x = 42;").

Re: Some of the error messages produced by Apple's MPW C compiler (2006)

#29
post #6
post #3

Is anyone at Apple allowed to have a sense of humor anymore?

Craig Federighi finds a way.

Humor is subjective, but I've always found Craig's performative sense of humor to be more annoying than anything else. The smug brainiac shtick is so old at this point that the dude practically steps on Steve Ballmer's feet.

Re: Some of the error messages produced by Apple's MPW C compiler (2006)

#30
post #2

MPW is the Macintosh Programmer's Workbench. I had forgotten about these. I think my first real push with MPW was using it as an environment to host the AT&T C++ compiler, which at that time was still a bunch of preprocessor macros written by Bjarne himself.

I was introduced to MPW when I started at Apple in 1995. I started on Quickdraw GX (if anyone remembers that).

Not specifically related to MPW, more about the times, a clean compile of the Quickdraw GX framework took something like eight hours. (Fortunately incremental builds were much quicker.) Nonetheless, it was common to kick off a clean build as you were leaving the office for the night.

Funny to think about that compiler compiling all night as I had dinner, watched a little cable TV, got some sleep....

Post reply on HN