Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!rex!ames!amdahl!pacbell!dsinc!syd From: syd@dsinc.DSI.COM (Syd Weinstein) Newsgroups: comp.mail.elm Subject: Re: readmsg bug Message-ID: <129@dsinc.DSI.COM> Date: 8 May 89 19:59:47 GMT References: <25537@amdcad.AMD.COM> Reply-To: syd@dsinc.UUCP (Syd Weinstein) Organization: Datacomp Systems, Inc., Huntingdon Valley, PA 19006 Lines: 21 In article jv@mh.nl (Johan Vromans) writes: :What is the need for the "readmsg" program? It looks to me that it is :lots of overhead to use an external tool to extract messages from the :mailboxes. Each time it has to scan the whole file, parsing headers, :counting messages, copying them etc etc ... And it's error-prone: no :continuation-header lines, user-specified weedout list is not obeyed. :All information needed is present in Elm the moment it's needed. For the moment, the answer is because its there. Aside from its use as a separate program in shell scripts, which I have used it myself, Elm uses it because thats the way Dave Taylor wrote it. The Elm development group inherited the code at a point in time and readmsg was used and is being used. As Elm gets rewritten it will be considered whether it is proper to keep using readmsg in this fashion. -- ===================================================================== Sydney S. Weinstein, CDP, CCP Elm Coordinator Datacomp Systems, Inc. Voice: (215) 947-9900 syd@DSI.COM or {bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235