[comp.sys.mac.programmer] MPW 3Features question

fons@uxh.cso.uiuc.edu (03/23/89)

Could anyone tell if the static data limit for MPW 3.0 is greater than 32K?
In addition is there an enlargement of maximum code segment size?
                                                        Paul Fons
                                        University of Illinois
                                        Coordinated Science Laboratory
                                        1101 W. Springfield Av.
                                        Urbana, Illinois 61801 U.S.A.
                              email:   Fons@uiucvmd.bitnet or...
                                        Fons@uxh.cso.uiuc.edu

ech@pegasus.ATT.COM (Edward C Horvath) (03/27/89)

From article <53100002@uxh.cso.uiuc.edu>, by fons@uxh.cso.uiuc.edu:
 
> Could anyone tell if the static data limit for MPW 3.0 is greater than 32K?
> In addition is there an enlargement of maximum code segment size?

There is a compiler option in MPW C 3.0 to permit >32K data (I haven't looked
at the pascal 3.0 manual yet).  Segments can be >32K (and could in 2.0), but
there remains the constraint that all externally-referenced entry points
in the segment have to be in the first 32K (segment-loader offsets).

I had the pleasant experience tonight of actually doing a compile in
BACKGROUND under MultiFinder, using MPW 3.0.  This was using (*ahem*) the
Aztec 3.6 tools, unchanged (and they laughed when I added spinning cursor
support!) to compile, assemble etc. under control of a shell script (output
of MPW make).  Being able to say (in effect) "make &" pretty well doubles
my productivity at the Mac.

I just took MPW 3.0 out of the box, and (despite intensive use of MPW 2.x for
almost two years) it looks like it'll take a couple of weeks to a couple of
months to come up to speed.  The boys in Cupertino have been very busy,
and they have added a LOT of VERY NICE stuff to the MPW environment.  Enough
nonsense about how expensive MPW is: this product is a class act.

The only disappointment is that I'll need a massive memory transfusion before
I'll be able to use the symbolic debugger; pity, if it is up to the
standards of the rest of the package it'll be nice to have (eventually).
Oh well, I've gotten this far with TMON...

=Ned Horvath=

Disclaimer(s):  I used to work for Manx but don't any more; I have nothing
to do with C++ except working for the same company as research!bs; and I
admire Apple from afar (mainly the far side of my checkbook).