From owner-freebsd-current@FreeBSD.ORG Tue Jun 3 16:10:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD47937B401; Tue, 3 Jun 2003 16:10:23 -0700 (PDT) Received: from mx0.freebsd-services.com (survey.codeburst.net [195.149.39.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27B4443F3F; Tue, 3 Jun 2003 16:10:23 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from [192.168.7.2] (freebsd.gotadsl.co.uk [81.6.249.198]) by mx0.freebsd-services.com (Postfix) with ESMTP id 308FB1B212; Wed, 4 Jun 2003 00:10:22 +0100 (BST) From: Paul Richards To: Poul-Henning Kamp In-Reply-To: <27696.1054681432@critter.freebsd.dk> References: <27696.1054681432@critter.freebsd.dk> Content-Type: text/plain Organization: Message-Id: <1054595310.1641.57.camel@cf.freebsd-services.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 03 Jun 2003 00:08:31 +0100 Content-Transfer-Encoding: 7bit cc: "M. Warner Losh" cc: dfr@freebsd.org cc: current@freebsd.org Subject: Re: VFS: C99 sparse format for struct vfsops X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2003 23:10:24 -0000 On Wed, 2003-06-04 at 00:03, Poul-Henning Kamp wrote: > In message <1054590840.1641.12.camel@cf.freebsd-services.com>, Paul Richards wr > ites: > >On Tue, 2003-06-03 at 22:36, Poul-Henning Kamp wrote: > > >> I thought the point in KOBJ was that it was extensible so you could > >> KLD load stuff which added more methods ? > > > >Not exactly. It allows for dynamic binding of methods that implement a > >specified interface. It gives you 2 things mainly: > > > >The possible methods available in an interface are fixed, they're > >defined in the .m files. > > Then I don't see the justification for the hashing & caching when it > can be resolved at compile time... kobj basically provides us with some OO type functionality. The linkage can't be determined at compile time since you don't know what methods an object is going to implement or what actual function implements a particular method until the object is instantiated, it's sort of late binding. -- Tis a wise thing to know what is wanted, wiser still to know when it has been achieved and wisest of all to know when it is unachievable for then striving is folly. [Magician]