Date: Fri, 10 May 2002 01:10:04 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: John Baldwin <jhb@FreeBSD.ORG>, "Michael C. Wu" <keichii@iteration.net>, obrien@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: syscall changes to deal with 32->64 changes. Message-ID: <20020510081004.GA4266@dhcp01.pn.xcllnt.net> In-Reply-To: <200205100656.g4A6uZgF031059@apollo.backplane.com> References: <XFMail.20020510011352.jhb@FreeBSD.org> <200205100656.g4A6uZgF031059@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 09, 2002 at 11:56:35PM -0700, Matthew Dillon wrote: > > :> Vendor imported code (e.g. KAME(sigh..), USB, possibly 1394, > :> cardbus, possibly some userland important tools and libraries) > :> would have little or no diffs from the original vendor's code.. > : > :Erm, all the changes so far aren't in API's, but rather changing the size > :of types like time_t. The same KAME code would compile fine. > : > > Huh? Changing the size of time_t sure sounds like an API change to me! There's no programmer visual change if you change the size of a type. Only when you go down to the binary level, you'll notice things have changed. I think this means that changing the definition of an abstract type (which time_t is) is not an API change. Put differently: you don't have to recode, just recompile (provided you didn't make assumptions about the size of course :-) I'm not 100% sure, but it's how I intuitively interpret API... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020510081004.GA4266>