home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!malgudi.oar.net!hyperion!desire.wright.edu!jmatthews
- From: jmatthews@desire.wright.edu
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: THINK Pascal Misconceptions (was Re: Summary: THINK Pascal...)READ/NEW
- Message-ID: <1992Nov20.002623.5717@desire.wright.edu>
- Date: 20 Nov 92 00:26:22 EST
- References: <Bxy2Iz.1w7@news.udel.edu> <Bxy4ty.B84@world.std.com>
- Organization: Wright State University
- Lines: 25
-
- In article <Bxy4ty.B84@world.std.com>, siegel@world.std.com (Rich Siegel) writes:
- > In Kurisoto's summary of responses to his problem (one of which is mine)
- > he quotes several of his respondents, some of whom provide advice which
- > is half-baked at best.
-
- >>(Person E wrote)
- >>> TP does several things for you in the runtime environment: local (stack)
- >>> vars are initialized to zero; your explicit stack and memory allocations
- >>> get set up; there are lots of subtle differences having to do with TP
- >>> sitting between you and the system; your code executes in a heap zone
- >>> in TP's heap zone; etc.
-
- > Mostly wrong. Local variables are not initialized to zero. Either under the
- > environment or standalone, local variables, except for arguments passed
- > in, will contain whatever random junk happens to be in the portion of
- > memory which corresponds to the link frame that you're using.
-
- As Persons C, E and G, I'll have to claim two outta three ain't bad:-)
- Rich is right; local vars are not initialized. I must have eaten some
- half-baked space-potatoes or forgotten my heavy boots and floated away:-)
-
- o----------------------------------------------------------------------------o
- | John B. Matthews, jmatthews@desire.wright.edu, disclaimer:= myViews <> WSU |
- | "Whom the gods would destroy, they first invite to program in C" |
- o----------------------------------------------------------------------------o
-