From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: file as a directory Date: Tue, 10 May 2005 11:52:24 -0700 Message-ID: <428102E8.2020509@namesys.com> References: <2c59f00304112205546349e88e@mail.gmail.com> <41A1FFFC.70507@hist.no> <41A21EAA.2090603@dbservice.com> <41A23496.505@namesys.com> <1101287762.1267.41.camel@pear.st-and.ac.uk> <1115717961.3711.56.camel@grape.st-and.ac.uk> <4280CAEF.5060202@namesys.com> <1115739129.3711.117.camel@grape.st-and.ac.uk> <4280E1A9.3010703@propylon.com> <4280EEA7.9080403@namesys.com> <4280F1D5.3060607@propylon.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <4280F1D5.3060607@propylon.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: sean.mcgrath@propylon.com Cc: Peter Foldiak , linux-kernel@vger.kernel.org, reiserfs-list@namesys.com Sean McGrath wrote: > Hans Reiser wrote: > >> Sean McGrath wrote: >> >> >> >>> The thing that interests me most is the difference (if any) between >>> giving a stream of bytes an opaque name e.g. "Chapter 1 of my >>> book.sxw" versus giving a stream of bytes a query expression that can >>> also be considered an opaque name e.g. >>> "/book/chapter[1] " >>> >>> >> >> What is an opaque name? >> >> >> >> > By "opaque name" I mean a name that is purely a label. A name that > cannot be interpreted as a query expression. Isn't query just another name for name? > > Sean > > > > >