Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!osu-cis!tut!mdf From: mdf@tut.UUCP Newsgroups: comp.sources.bugs Subject: Re: Microemacs 3.9 spawn.c #if problems Message-ID: <2327@tut.cis.ohio-state.edu> Date: Wed, 25-Nov-87 23:55:42 EST Article-I.D.: tut.2327 Posted: Wed Nov 25 23:55:42 1987 Date-Received: Sun, 29-Nov-87 03:42:59 EST References: <2151@tut.cis.ohio-state.edu> <4755@iucs.UUCP> Reply-To: mdf@tut.cis.ohio-state.edu.UUCP (Mark D. Freeman) Organization: StrongPoint Systems, Inc.; Columbus, OH. (guest of Ohio State U.) Lines: 30 In <4755@iucs.UUCP> bobmon@iucs.UUCP writes: >I wrote: >>In spawn.c, the "#if"s are inconsistant in the case of MSDOS and MSC. >>This concerns the use of "system()" vs. functions defined in spawn.c > >[On rereading, I'm not as sure whether Mark is referring to v3.9 or v3.9e. >I assume he means v3.9 the original, not 3.9e.] > Unfortunately, my problem is in 3.9e. >BY THE WAY: in v3.9e, this is all VERY different. Apparently Dan >Lawrence is replacing the system() call entirely with his own call, >with some additional functionality. My problem concerns the #if statements used to determine when to use the new calls and when to use system(). Help?! -- Mark D. Freeman (614) 262-3703 StrongPoint Systems, Inc. mdf@tut.cis.ohio-state.edu 2440 Medary Avenue ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!mdf Columbus, OH 43202-3014 Guest account at The Ohio State University