Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266876AbUIJHFD (ORCPT ); Fri, 10 Sep 2004 03:05:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266808AbUIJHEX (ORCPT ); Fri, 10 Sep 2004 03:04:23 -0400 Received: from rwcrmhc12.comcast.net ([216.148.227.85]:4304 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S267278AbUIJG5P (ORCPT ); Fri, 10 Sep 2004 02:57:15 -0400 Message-ID: <4141504B.8030104@namesys.com> Date: Thu, 09 Sep 2004 23:57:15 -0700 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Foldiak CC: Timothy Miller , Jamie Lokier , Adrian Bunk , viro@parcelfarce.linux.theplanet.co.uk, Linus Torvalds , Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , ReiserFS List Subject: Re: silent semantic changes with reiser4 References: <20040825200859.GA16345@lst.de> <20040825204240.GI21964@parcelfarce.linux.theplanet.co.uk> <20040825212518.GK21964@parcelfarce.linux.theplanet.co.uk> <20040826001152.GB23423@mail.shareable.org> <20040826003055.GO21964@parcelfarce.linux.theplanet.co.uk> <20040826010049.GA24731@mail.shareable.org> <412DA40B.5040806@namesys.com> <20040826140500.GA29965@fs.tum.de> <20040826150202.GE5733@mail.shareable.org> <41410DE7.3090100@techsource.com> <41413A2B.9020405@namesys.com> <1094797973.4838.4.camel@almond.st-and.ac.uk> In-Reply-To: <1094797973.4838.4.camel@almond.st-and.ac.uk> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1131 Lines: 42 Peter Foldiak wrote: >On Fri, 2004-09-10 at 06:22, Hans Reiser wrote: > > >>He asked me, why not just access a filename's size as filename/size? >> >> > >I now understand that you need a way to distinguish between something >like > >shoe/size > >and > >shoe/.../size (or shoe/..size) > >The first one is the size of the shoe, the second is the automatically >generated size of the file (object). You would get into trouble if you >would not allow the user to use shoe/size for shoe size. Peter > > > > > > exactly. Of course, problem/shoe/size could refer to shoe size in centimeters of a problem shoe or the size of the problem relating to a shoe in units of reporters providing press coverage of it or.... So there are lots of opportunities for ambiguity in semantics.... Still, widely used builtins seem like they should be moderately evasive of commonly used names. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/