From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,15edb893ef79e231 X-Google-Attributes: gidfac41,public X-Google-Thread: f4fd2,23202754c9ce78dd X-Google-Attributes: gidf4fd2,public X-Google-Thread: 103376,15edb893ef79e231 X-Google-Attributes: gid103376,public X-Google-Thread: 114809,15edb893ef79e231 X-Google-Attributes: gid114809,public X-Google-ArrivalTime: 2002-01-23 08:01:50 PST Path: archiver1.google.com!news1.google.com!postnews1.google.com!not-for-mail From: gmc444@yahoo.com (Greg C) Newsgroups: comp.lang.lisp,comp.lang.ada,comp.lang.eiffel,comp.lang.smalltalk Subject: Re: True faiths ( was Re: The true faith ) Date: 23 Jan 2002 08:01:49 -0800 Organization: http://groups.google.com/ Message-ID: <62340e2a.0201230801.7b82c8ed@posting.google.com> References: <9jtu3u8cq92b05j47uat3412tok6hqu1ki@4ax.com> <3C3F8689.377A9F0F@brising.com> <3219936759616091@naggum.net> <3C483CE7.D61D1BF@removeme.gst.com> <7302e4fa4a.simonwillcocks@RiscPC.enterprise.net> <3C4D9B03.60803@mail.com> <3C4DE336.3080102@worldnet.att.net> NNTP-Posting-Host: 65.209.183.161 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1011801710 18833 127.0.0.1 (23 Jan 2002 16:01:50 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 23 Jan 2002 16:01:50 GMT Xref: archiver1.google.com comp.lang.lisp:25075 comp.lang.ada:19239 comp.lang.eiffel:5508 comp.lang.smalltalk:18528 Date: 2002-01-23T16:01:50+00:00 List-Id: Jim Rogers wrote in message news:<3C4DE336.3080102@worldnet.att.net>... [...] > Copying pointers and using GC or even reference counting is a very > nice solution for single threaded applications. It becomes a very > messy solution for multi-threaded applications. Now all those > copied pointers need to be protected from inappropriate simultaneous > access by several threads. > LOL! Jim, this sounds like an excellent example of a problem where it's important to distinguish between deep and shallow copy operators, which has been a large part of the debate in this thread in the first place... Greg