[comp.sys.mac.programmer] MPW vs. Think code production

jess@gn.ecn.purdue.edu (Jess M Holle) (06/25/91)

I posted a question on this topic over the weekend, but it appears that it
didn't make it to the net or something (our news was flakey at the time).

Anyway...

I have read a lot of varying opinions on the relative size and speed of code
output by Think and MPW (C and Pascal of each in particular). Does anybody
have any real program timings or code sizes that point one way or the other?
Are there any areas where MPW's code production seems better than Think's, or
vice versa? If MPW's code is slower/bigger, why are it's compilers and linkers
so much slower? Are they being improved speed-wise and code-efficiency-wise?

I ask this because I have MPW Pascal and C now. It seems, however, that unless
Think just does not enter into your niche (e.g. C++) that there is little
reason to use MPW. This is making me think of switching to Think C (I rarely
use Pascal) and selling my MPW software, rather than upgrading MPW. I probably
won't since I have learned to use MPW and am not in the mood to learn another
environment, but I would like to know that all the money that I'll be pouring
into an upgrade might someday bring me a faster/better code-producing 
compiler/linker.

Jess Holle