Live data from Hacker News

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

cs.cmu.edu

51–60 of 154 posts

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

#52
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...

Maybe this is it?

http://telcontar.net/Screenshots/worldwidewonk/Amazon-404-eh...

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

#53

Earlier quoted context omitted.

I understand the arguments for unified RAM on a SoC, but it’s still a shame; even the new Mac Pro doesn’t have RAM slots.

The soldered-in SSD is worse, though. The SSD WILL wear out, so then you get to throw away your Mac?

Just like AirPods and AirPods Pro when their 7 cents worth of batteries die! A perfect system.

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

#54
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.

There’s nothing stopping anyone from going back and using all of that old software exclusively. For some reason everyone prefers the newer software, though. Perhaps there’s more to it than binary size?

Binary size on a desktop OS is almost totally irrelevant in practice. Memory size matters a little more, but your OS will generally do a good job of loading what it needs (ie, huge binaries can still start quickly) and paging out what it doesn't.

People have aesthetic complaints about "bloat", but again this is orthogonal to the actual speed of anything.

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

#55
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.

There’s nothing stopping anyone from going back and using all of that old software exclusively. For some reason everyone prefers the newer software, though. Perhaps there’s more to it than binary size?

> There’s nothing stopping anyone from going back and using all of that old software exclusively.

Monthly bills are stopping me. Can I use Apple's MPW C compiler to build for iOS?

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

#56
post #46
post #27

Earlier quoted context omitted.

No. The compiler knows that trick for its own code :) not sure about introspecting into the assembly (I think LLVM doesn't do that). But either way, standard C returns int of 0 from main on success. So: ldx #0 txa rts

Nitpick: this isn’t standard C (it uses void main , not int main ) Nitpick 2: why ldx #0 txa rts ? I would think lda #0 rts is shorter and faster Back to my question: if it can’t, the claim “an assembler programmer couldn't do better” isn’t correct. I think an assembler programmer for the 6502 would consider doing a jmp at the end, even if it makes the function return an incorrect, possibly even unpredictable value.…

I bet that sizeof(int)==2 - which immediately tells you everything you need to know - and the return value from a function has 8 bits in X and 8 bits in A. So ldx#0:txa is how you load a return value of (int)0.

Regarding this specific unrolled loop, I would expect a 6502 programmer would just write the obvious loop, because they're clearly optimizing for space rather than speed when calling the ROM routine. They'll be content with the string printing taking about as long as it takes, which clearly isn't too long, as they wouldn't have done it that way otherwise. And the loop "overhead" won't be meaningful. (Looks like it'll be something like 7 cycles per character? I'm not familiar with the Apple II. Looks like $fbfd preserves X though.)

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

#57
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…

Where does this playfulness persist? I miss it too.

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

#58
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…

Where does this playfulness persist? I miss it too.

The punishments continued until the playfulness went away.

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

#59
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…

Where does this playfulness persist? I miss it too.

HTTP status code 418?
Post reply on HN