From owner-freebsd-chat@FreeBSD.ORG Sat Mar 6 02:31:09 2004 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30FA016A4CE for ; Sat, 6 Mar 2004 02:31:09 -0800 (PST) Received: from lilzmailso02.liwest.at (lilzmailso02.liwest.at [212.33.55.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBF2643D1F for ; Sat, 6 Mar 2004 02:31:08 -0800 (PST) (envelope-from dgw@liwest.at) Received: from cm58-27.liwest.at ([212.33.58.27]) by lilzmailso02.liwest.at with esmtp (Exim 4.24) id 1AzZ5D-00008j-FL; Sat, 06 Mar 2004 11:31:03 +0100 From: Daniela To: Rahul Siddharthan , Chris Pressey Date: Sat, 6 Mar 2004 11:25:47 +0000 User-Agent: KMail/1.5.3 References: <20040306012556.GA2554@online.fr> <20040305192200.7a377e92.cpressey@catseye.mine.nu> <20040306031954.GA3713@online.fr> In-Reply-To: <20040306031954.GA3713@online.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403061125.47751.dgw@liwest.at> cc: chat@freebsd.org Subject: Re: FreeBSD Most wanted X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 10:31:09 -0000 On Saturday 06 March 2004 03:19, Rahul Siddharthan wrote: > Chris Pressey said on Mar 5, 2004 at 19:22:00: > > On Sat, 6 Mar 2004 02:55:35 +0100 > > > > Rahul Siddharthan wrote: > > > Daniela wrote: > > > > I like doing AI programming, that's numbercrunching most of the time. > > > > > > > > A compiler can't, for example, know whether you need to have zero > > > > returned from the atoi() function when the user entered nonsense. If > > > > you don't need to check whether the user has entered a valid number, > > > > you can do it *much* faster. > > > > > > Excellent example. Here you're limited by the speed of the fingers of > > > the user who's entering the data, so there's *absolutely no point* in > > > optimising the atoi() function in this way. (Or if you're reading from > > > the disk, the disk I/O will be the bottleneck, though it's admittedly > > > faster than fingers.) > > > > I don't understand your point... atoi() is not an I/O function. > > Where did the "a" in the "atoi" come from? > > The point is that some very slow i/o routine gives you an ascii string > (that's the only reason you'd ever need to deal with an ascii string), > and then the C library's atoi() converts that to an integer. Now, > what's the advantage of optimising atoi()? It was just an example.