From owner-freebsd-chat@FreeBSD.ORG Fri Mar 5 19:17:02 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 CE62C16A4CF for ; Fri, 5 Mar 2004 19:17:02 -0800 (PST) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7187243D1D for ; Fri, 5 Mar 2004 19:17:02 -0800 (PST) (envelope-from cpressey@catseye.mine.nu) Received: from catseye.biscuit.boo ([154.5.85.228]) by priv-edtnes51.telusplanet.netSMTP <20040306031702.BEPY9497.priv-edtnes51.telusplanet.net@catseye.biscuit.boo>; Fri, 5 Mar 2004 20:17:02 -0700 Date: Fri, 5 Mar 2004 19:22:00 -0800 From: Chris Pressey To: Rahul Siddharthan Message-Id: <20040305192200.7a377e92.cpressey@catseye.mine.nu> In-Reply-To: <1078538135.40492f9742e70@imp4-q.free.fr> References: <20040306012556.GA2554@online.fr> <200403060245.05790.dgw@liwest.at> <1078538135.40492f9742e70@imp4-q.free.fr> Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: 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 03:17:02 -0000 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. -Chris