Live data from Hacker News

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

cs.cmu.edu

11–20 of 154 posts

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

#11

  "a typedef name was a complete surprise to me at this point in your program" 
Ah, the joys of fun compiler messages. I miss those days. I remember getting one from a vendor compiler that was:

  "No! But they'll only let me warn you. Danger Will Robinson! Danger!"
and:

  "Really! If you are fussing around with void *, just go home or at least back to your editor!"
I think the IT manager kept that as a vendor just because of the message (the SDK was meh, but also fun!).

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

#12
post #7
post #2

I miss this kind of playfulness in computing. When I was at Amazon my manager told me that several years earlier he was responsible for updating the 404 page so he scanned a picture of a cat his daughter drew and made that the body of the page. In 2009 when I started, that was still the image, but at some point someone must have noticed and replaced it with a stock photo of a dog. The asset was still called kayli-kit…

Maybe the daughter sued for copyright infringement when she turned 18. ;) Serious question: Is this possible when a guardian gave consent earlier?

I know you’re joking, but she wasn’t 18 yet before they changed the picture.

AFAICT, kids own the copyright to things they create[0], but guardians are responsible and can use it on the child’s interest. IANAL, consult an attorney, etc., etc.

0 - https://www.copyright.gov/help/faq/faq-who.html#:~:text=Can%....

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

#13
My favourite syntax error message produced by the Glockenspiel C++ compiler (a cfront derived piece of junk that I used in a training company in the early 90s) was simply "core dumped". This was slightly tricky to explain to people already struggling with C++, and who had paid us money for the course.

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

#14
post #8
post #2

I miss this kind of playfulness in computing. When I was at Amazon my manager told me that several years earlier he was responsible for updating the 404 page so he scanned a picture of a cat his daughter drew and made that the body of the page. In 2009 when I started, that was still the image, but at some point someone must have noticed and replaced it with a stock photo of a dog. The asset was still called kayli-kit…

> The compiler is 324k in size Playfulness isn't the only thing we've lost. Software bloat has reached comedic levels.

The clang executable on my machine is 18kb.

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

#15
post #2

I miss this kind of playfulness in computing. When I was at Amazon my manager told me that several years earlier he was responsible for updating the 404 page so he scanned a picture of a cat his daughter drew and made that the body of the page. In 2009 when I started, that was still the image, but at some point someone must have noticed and replaced it with a stock photo of a dog. The asset was still called kayli-kit…

> picture of a cat

I couldn't find this elusive picture of a cat on archive.org, but I found this dog instead:

https://web.archive.org/web/20030113144310/https://www.amazo...

June 2016 appears to be when Amazon adopted the current error pages with the large dog images.

https://web.archive.org/web/20160612232820/http://www.amazon...

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

#16
post #8
post #2

I miss this kind of playfulness in computing. When I was at Amazon my manager told me that several years earlier he was responsible for updating the 404 page so he scanned a picture of a cat his daughter drew and made that the body of the page. In 2009 when I started, that was still the image, but at some point someone must have noticed and replaced it with a stock photo of a dog. The asset was still called kayli-kit…

> The compiler is 324k in size Playfulness isn't the only thing we've lost. Software bloat has reached comedic levels.

Your optimizing compiler today will actually optimize. LLVM was recently ported to the 6502 (yes, really) [1]. An example:

    void outchar (char c) { 
        c = c | 0x80;
        asm volatile ("jsr $fbfd\n" : : "a" (c): "a");
    }

    void outstr (char* str) {
        while (*str != 0) 
            outchar(*str++);
    }

    void main () {
        outstr("Hello, world!\n");
    }
That is compiled to this:

    lda #$c8       ; ASCII H | 0x80
    jsr $fbfd
    lda #$e5       ; ASCII e | 0x80
    jsr $fbfd
    ...
Unrolled loop, over a function applied to a constant string at compile time. An assembler programmer couldn't do better. It is the fastest way to output that string so long as you rely on the ROM routine at $fbfd. (Apple II, for the curious.) Such an optimizing transform is unremarkable today. But stuff like that was cutting edge in the 90s.

[1] https://llvm-mos.org/wiki/Welcome

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

#17
post #13

My favourite syntax error message produced by the Glockenspiel C++ compiler (a cfront derived piece of junk that I used in a training company in the early 90s) was simply "core dumped". This was slightly tricky to explain to people already struggling with C++, and who had paid us money for the course.

The users could simply run a debugger to get a backtrace from the core file... then with some experience, they would learn to associate different hex addresses with different kinds of errors. No harm, no foul.

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

#18
post #5

Previous discussion: https://news.ycombinator.com/item?id=30238928 To inline my comment in the previous thread: 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.…

[deleted]

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

#19
post #8

Earlier quoted context omitted.

> The compiler is 324k in size Playfulness isn't the only thing we've lost. Software bloat has reached comedic levels.

The clang executable on my machine is 18kb.

I bet it forks some other executables, though...
Post reply on HN