Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Jan 2007 08:54:09 -0700
From:      "Coleman Kane" <zombyfork@gmail.com>
To:        "Peter Jeremy" <peterjeremy@optushome.com.au>
Cc:        scottl@samsco.org, src-committers@freebsd.org, netchild@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org, sam@errno.com, Max Laier <max@love2party.net>, "M. Warner Losh" <imp@bsdimp.com>
Subject:   Re: cvs commit: src/sys/compat/linprocfs linprocfs.c
Message-ID:  <346a80220701220754u7facfb37n4c02d99007fee32c@mail.gmail.com>
In-Reply-To: <20070122073555.GA837@turion.vk2pj.dyndns.org>
References:  <45B28A31.4080604@samsco.org> <20070121131229.014eda2e@Magellan.Leidinger.net> <20070121.084719.-233674217.imp@bsdimp.com> <200701212037.25404.max@love2party.net> <20070122073555.GA837@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 1/22/07, Peter Jeremy <peterjeremy@optushome.com.au> wrote:
>
> On Sun, 2007-Jan-21 20:36:39 +0100, Max Laier wrote:
> >That's right, but I think we can fix it by simply making int64_t an alias
> >for "long long" on all architectures.  I still haven't heard any reason
> >not to just do this - is there something, other than historical?
>
> Or we could re-write the kernel in C++ so that the various inttypes
> know how to print themselves without programmers trying to second-
> guess what the underlying type of foo_t is.  :-) :-)
>
> --
> Peter Jeremy
>
>
>
Yeah, and then we could start rewriting everything in a new package called
libkern++, fun!

--
coleman



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?346a80220701220754u7facfb37n4c02d99007fee32c>