Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!unisoft!hoptoad!hsfmsh!mhyman
From: mhyman@hsfmsh.UUCP (Marco S. Hyman)
Newsgroups: comp.object
Subject: Re: Reentrant code
Summary: Should be reentrant
Keywords: reentrant code, object methods
Message-ID: <1487@hsfmsh.UUCP>
Date: 3 Oct 89 15:00:20 GMT
References: <11242@eerie.acsu.Buffalo.EDU>
Reply-To: mhyman@hsfmsh.UUCP (Marco S. Hyman)
Organization: Softcom, Inc.  San Francisco
Lines: 19

In article <11242@eerie.acsu.Buffalo.EDU> axaris@cs.buffalo.edu (Vassilios Axaris) writes:
    I have recently read somewhere (most likely a magazine article) that
    object oriented code must be non reentrant. Is this statement true?
    For some reason, I do not believe it is, since code is shared by
    objects through inheritance.  But I want to be sure...

If I were bold enough to make a rash statement I would say that
object-oriented code MUST be reentrant. However, I don't like absolutes.

Think of the code for a class as being owned by a class and shared by all
objects of the class. In many cases multiple instances of the class
(objects) will be active.  This is especially true in simulation systems,
a natural used for OO programming.


--marc
-- 
// Marco S. Hyman			home:  {ames,sun}!pacbell!dumbcat!marc
// UUCP: ...!hoptoad!hsfmsh!mhyman	I-net: hsfmsh!mhyman@sfsun.west.sun.com