Date: Thu, 11 Apr 2013 11:31:06 -0700 From: Garrett Cooper <yaneurabeya@gmail.com> To: Colin Percival <cperciva@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Gleb Smirnoff <glebius@freebsd.org>, src-committers@freebsd.org, Bruce Evans <brde@optusnet.com.au> Subject: Re: svn commit: r249355 - head/lib/libkvm Message-ID: <6ABB36AE-A7AB-4A06-82B9-5E3F07F18AAC@gmail.com> In-Reply-To: <5166FD40.6040102@freebsd.org> References: <201304110730.r3B7Uo6d067302@svn.freebsd.org> <20130411175308.Q1435@besplex.bde.org> <5166FD40.6040102@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 11, 2013, at 11:13 AM, Colin Percival wrote: > On 04/11/13 00:59, Bruce Evans wrote: >>> Log: >>> Include types.h for C99 uintXX_t types. >>=20 >> This adds namespace pollution that was carefully left out. >=20 > ... and as a developer, I wish we left out such namespace pollution = more often. >=20 > I write code on FreeBSD which I then publish with the intention that = people will > be able to use it on any POSIX-compliant system, and I've lost count = of the > number of times I've been hit by "this won't build on OS X or Linux = because you > forgot to #include <stdint.h>". Funny this would be mentioned. I've seen the converse a lot with = Linux devs because they fail to understand that headers on Linux = #include a lot more crud than they need to.. Devs in general don't read the [POSIX] manpages like they should = to figure out what needs to be #include'd in order to get = function/constant definitions. Third party devs are usually the worst = offenders. Thanks, -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ABB36AE-A7AB-4A06-82B9-5E3F07F18AAC>