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 autolearn=unavailable autolearn_force=no version=3.4.4 Path: Xl.tags.giganews.com!border1.nntp.ams3.giganews.com!border1.nntp.ams2.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!proxad.net!feeder2-2.proxad.net!nx02.iad01.newshosting.com!newshosting.com!216.196.98.144.MISMATCH!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Mon, 23 Sep 2013 17:06:32 -0500 Newsgroups: comp.lang.ada Date: Mon, 23 Sep 2013 18:06:30 -0400 From: "Peter C. Chapin" X-X-Sender: peter@whirlwind Subject: Re: Anti-Ada FUD (rant) In-Reply-To: Message-ID: References: <2f813569-5ff8-4c20-a5ab-8538e6514906@googlegroups.com> <6a978d1c-1922-448b-91f7-cf8a19eab1fd@googlegroups.com> <1lgdqz079ogp5.1ti8931i9me3x$.dlg@40tude.net> <8203a0cd-5238-4086-8ca0-1c6c1b3fec09@googlegroups.com> <1ixhazoag8y0l.4mpw6pmi83xm.dlg@40tude.net> <51a27fa6-027d-4655-a78c-6a582811e23f@googlegroups.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-ng4nvf0tHh96oh2fmPvOV8xRjABfIPzH1+ObHKm2og2fhctvtLIYV2KbORWpYByjm6go7a+jYdm6V77!hzcVx3Lo4vGJXRqSMLnV9bc7NdSq7XOPQMg8IlgRcI5iT3xvQ0bQeuY1cQAhqrNLMQphRzqxLQ== X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2526 Xref: number.nntp.dca.giganews.com comp.lang.ada:183424 Date: 2013-09-23T18:06:30-04:00 List-Id: On Mon, 23 Sep 2013, Peter Brooks wrote: > That's why I'm asking, if there's a genuine reason why there's something > wrong with fork/exec, I'm keen to know it, not as Unix bashing, but > because I'd like to know what better solution there might be. It seems to me that an efficient implementation of fork/exec relies on memory management tricks such as copy on write and such. This is fine if you are using a processor with hardware support for such things but in some small scale embedded environments it might be a problem. Peter