Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!rutgers!att!pegasus!ech
From: ech@pegasus.ATT.COM (Edward C Horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: XFCN/XCMD string in LSC C v3.0
Message-ID: <2788@pegasus.ATT.COM>
Date: 14 Apr 89 18:41:39 GMT
References: <1583@ccnysci.UUCP>
Organization: AT&T ISL Middletown NJ USA
Lines: 17

From article <1583@ccnysci.UUCP>, by alexis@ccnysci.UUCP (Alexis Rosen):

> Perhaps I'm being dense (it's 5AM), but why can't compilers just see that
> they're creating a stand-alone resource and put the "globals" in a stack
> frame?

You're not dense: the easiest way for a pascal programmer to end-run the
globals problem is to declare a "main" PROCEDURE and nest all the
subroutines within it.  If the codeRes is small enough, no worries.

C programmers, lacking nested procedures, are underwhelmed by this
solution.  Thus Aztec C and LSC both provide for globals in code resources.
MPW C does not.

Hmm, I wonder who drives the MPW bus...

=Ned Horvath=