The History of Mac Office, Part I

Buggin My Life Away The History of Mac Office Part I | garden statues

Buggin My Life Away The History of Mac Office Part I | garden statues — Fri, 19 Jun 2009 11:53:05 GMT

PingBack from http://gardenstatuesgalore.info/story.php?id=1645

Buggin My Life Away The History of Mac Office Part I | wheelbarrow

Buggin My Life Away The History of Mac Office Part I | wheelbarrow — Fri, 19 Jun 2009 09:25:43 GMT

PingBack from http://wheelbarrowstyle.info/story.php?id=1115

Buggin My Life Away The History of Mac Office Part I | Hair Growth Products

Buggin My Life Away The History of Mac Office Part I | Hair Growth Products — Wed, 10 Jun 2009 05:40:24 GMT

PingBack from http://hairgrowthproducts.info/story.php?id=1359

Buggin My Life Away The History of Mac Office Part I | Cellulite Creams

Buggin My Life Away The History of Mac Office Part I | Cellulite Creams — Wed, 10 Jun 2009 04:58:51 GMT

PingBack from http://cellulitecreamsite.info/story.php?id=8489

Buggin My Life Away The History of Mac Office Part I | Wood TV Stand

Buggin My Life Away The History of Mac Office Part I | Wood TV Stand — Wed, 03 Jun 2009 03:19:29 GMT

PingBack from http://woodtvstand.info/story.php?id=53297

Buggin My Life Away The History of Mac Office Part I | Wood TV Stand

Buggin My Life Away The History of Mac Office Part I | Wood TV Stand — Mon, 01 Jun 2009 21:12:32 GMT

PingBack from http://woodtvstand.info/story.php?id=12109

re: The History of Mac Office, Part I

Rick Schaut — Wed, 14 Jun 2006 05:17:29 GMT

Gabe,

Machine limitations and disk speed trade-offs are why we continued to use p-code, but it wasn't the initial impetus behind p-code. The original impetus, however, was to provide some platform independence.

re: The History of Mac Office, Part I

Gabe — Wed, 14 Jun 2006 04:09:31 GMT

I once had a chance to speak with Doug Klunder (one of the original authors of Excel), and my recollections with regards to p-code are a bit different.

The first Macs had only 128k RAM and nothing but 400k floppies for storage. All 68k machine code was stored in CODE resources that were limited to 32k. Fitting a whole program into 128k was impossible, so CODE resources you didn't need could be discarded and new ones could be loaded from floppy -- which would be really slow.

The combination of 32k CODE limit and the need to avoid hitting the slow floppy meant that it was extremely important that code size be reduced. This was done with p-code. While being slower to execute than native code, it was smaller, thus faster to load.

Anything that had to be fast was compiled to native machine code, while everything else was a candidate for p-code. That was the only way to fit Excel into the original Mac, though the reasons to use it in later versions may have varied.

I recall that Microsoft's DOS compiler had a p-code option, so I don't know if it was a common thing at the time, or if MS created it for Excel, or if it predates both.

re: The History of Mac Office, Part I

Rosyna — Mon, 05 Jun 2006 01:36:48 GMT

FWIW, the preferences to set in Xcode can be found via Help->Show Expert Preferences. And they are..

PBXBuildFailureSound
Path to a sound file to play when a build fails. There is no default setting.

PBXBuildSuccessSound
Path to a sound file to play when a build succeeds. There is no default setting.

Schwieb » Blog Archive » Pseudo Code

Schwieb » Blog Archive » Pseudo Code — Sun, 04 Jun 2006 11:09:34 GMT

PingBack from http://www.schwieb.com/blog/archives/10