Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!srcsip!gorby!mnkonar From: mnkonar@gorby.SRC.Honeywell.COM (Murat N. Konar) Newsgroups: comp.object Subject: Re: Reentrant code Keywords: reentrant code, object methods Message-ID: <33425@srcsip.UUCP> Date: 2 Oct 89 18:46:29 GMT References: <11242@eerie.acsu.Buffalo.EDU> <1857@brazos.Rice.edu> Sender: news@src.honeywell.COM Reply-To: mnkonar@gorby.UUCP (Murat N. Konar) Organization: Honeywell Systems & Research Center, Camden, MN Lines: 19 In article <1857@brazos.Rice.edu> preston@titan.rice.edu (Preston Briggs) 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, > >Sounds wrongs to me. Perhaps someone's particular implementation >has this restriction, but most don't. It certainly isn't a requirement >specific to object oriented code. Seems wrong to me also. I thought that object oriented code SHOULD be re-entrant. This is because the code may be executed for multiple instances of a class or sub class. Or am I blowing smoke? ____________________________________________________________________ Have a day. :^| Murat N. Konar Honeywell Systems & Research Center, Camden, MN mnkonar@SRC.honeywell.com (internet) {umn-cs,ems,bthpyd}!srcsip!mnkonar(UUCP)