Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!fas-news.harvard.edu!newspump.wustl.edu!news.ecn.bgu.edu!usenet.ins.cwru.edu!howland.reston.ans.net!agate!darkstar.UCSC.EDU!news.hal.COM!decwrl!adobe!paleface.mv.us.adobe.com!user
From: cpage@mv.us.adobe.com (Chris Page)
Subject: Re: Dylan Runtime Environment
Message-ID: <cpage-1801951902320001@paleface.mv.us.adobe.com>
Sender: usenet@adobe.com (USENET NEWS)
Organization: Adobe Systems Incorporated
References: <9501131747.AA12748@locutus.quadralay.com> <REC.95Jan14163824@elf115.elf.org> <3fa0gv$2e4@cantaloupe.srv.cs.cmu.edu> <3fbif1$6ia@flop.mcom.com> <1995Jan18.190603.11397@gallant.apple.com>
Date: Thu, 19 Jan 1995 03:02:32 GMT
Lines: 35

In article <1995Jan18.190603.11397@gallant.apple.com>, Walter Smith
<wrs@apple.com> wrote:

> Ben Allums, allums@quadralay.com writes:
> > Since the Dylan runtime environment handles memory management for you,
> > Dylan programs should never have memory errors.
[...]
> This is a common issue on the Newton platform.
[...]
> For example, if you allocate a big array in a loop:
> 
>         loop begin
>                 x := Array(2000, nil);
>                 ...
>         end;
> 
> You really want to make sure the old array is dead before you allocate the
> new array.
[...]
>         loop begin
>                 x := nil;       // Allow old value to become garbage
>                 x := Array(2000, nil);
>                 ...
>         end;

This is going off-topic, but I thought the above assignment "x :=
Array(2000, nil);" would also effectively remove the original reference
held in "x", so "x := nil;" is redundant. Comments?

-- 
Chris Page                                   "I got a Power Macintosh...
Adobe Systems Incorporated                    ...now what?...
cpage@mv.us.adobe.com                         ...mmmm...Marathon!" -- Me

Disclaimer: opinions expressed are not necessarily those of my employer.
