Date: Fri, 09 May 2003 11:27:52 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: Paul Richards <paul@freebsd-services.com> Cc: freebsd-arch@FreeBSD.org Subject: Re: `Hiding' libc symbols Message-ID: <xzpfznobhbb.fsf@flood.ping.uio.no> In-Reply-To: <1052433233.619.27.camel@cf.freebsd-services.com> (Paul Richards's message of "08 May 2003 23:33:54 %2B0100") References: <Pine.BSF.4.21.0305011046140.73226-100000@InterJet.elischer.org> <XFMail.20030501140549.jhb@FreeBSD.org> <20030501182820.GA53641@madman.celabo.org> <20030503201409.GA41554@dragon.nuxi.com> <20030505175428.GA19275@madman.celabo.org> <20030506170919.GD36798@dragon.nuxi.com> <20030506175557.GE79167@madman.celabo.org> <20030508161223.GL1869@survey.codeburst.net> <xzpu1c5unx1.fsf@flood.ping.uio.no> <1052433233.619.27.camel@cf.freebsd-services.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Richards <paul@freebsd-services.com> writes: > On Thu, 2003-05-08 at 22:30, Dag-Erling Smorgrav wrote: > > Paul Richards <paul@freebsd-services.com> writes: > > > Any C code that isn't written according to the standard that defines > > > C is broken. > > That includes most of the FreeBSD source tree. > To some extent true, but we don't deliberately break the rules or > flagrantly disregard them. Yes, we do, because there are things that can't be done (at least not easily) within the standard. Using the same struct iovec for readv(2) and writev(2) results in const warnings, yet using different structs, or union tricks to make the same pointer be both const and not const, would result in significantly (and probably unacceptably) increased complexity and fragility. > > Now I know why people accuse us of elitism... > > > > Let's please not favor pedantry over robustness. > This isn't elitism. A professor or teacher is not elitist when they > correct the mistakes of less experienced pupils. FreeBSD should > highlight bad habits so people can see that they are making mistakes and > improve their skills. Our role is not to be the professor or teacher of the open source world, but rather to be the research technician who builds the tools that professors use in their research and teaching. As such, we should be aware that the professor is not solely interested in academically correct tools but also in tools that get the work done a little faster and a little cheaper, even if that means cutting corners or making concessions, so he can publish that paper and get that grant. DES -- Dag-Erling Smorgrav - des@ofug.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpfznobhbb.fsf>