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.<p>[1] <a href="https://en.m.wikipedia.org/wiki/Green_Hills_Software" rel="nofollow">https://en.m.wikipedia.org/wiki/Green_Hills_Software</a><p>[2] <a href="https://en.m.wikipedia.org/wiki/Macintosh_Programmer%27s_Workshop" rel="nofollow">https://en.m.wikipedia.org/wiki/Macintosh_Programmer%27s_Wor...</a><p>[3] <a href="https://web.archive.org/web/20140528005901/http://lists.apple.com/archives/MPW-Dev/2005/May/msg00003.html" rel="nofollow">https://web.archive.org/web/20140528005901/http://lists.appl...</a>
MPW is the Macintosh Programmer's Workbench.<p>I had forgotten about these.<p>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.
Ahh, I saw the "too many errors on one line" report once when playing with MPW.<p>A very underrated, idiosyncratic, clever development environment, somehow more reminiscent of Poplog than anything else I've used.
> 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<p>I get this issue a lot on modern compilers, when trying to write switch/macro-based coroutines (<a href="https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html" rel="nofollow">https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html</a>) in C++. Does anyone have a workaround? (I hope it doesn't involve C++20 coroutines... I still don't understand them.)
Original source: Tony Cunningham, rec.humor.funny, 7 August 1991<p><a href="https://groups.google.com/g/rec.humor.funny/c/knG5ONlInXM/m/Q8TDoEPNG4QJ" rel="nofollow">https://groups.google.com/g/rec.humor.funny/c/knG5ONlInXM/m/...</a>