From owner-freebsd-hackers Fri Jul 3 21:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06320 for freebsd-hackers-outgoing; Fri, 3 Jul 1998 21:07:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles85.castles.com [208.214.165.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06312 for ; Fri, 3 Jul 1998 21:07:30 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA07881; Fri, 3 Jul 1998 21:07:20 -0700 (PDT) Message-Id: <199807040407.VAA07881@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Wackerbarth cc: Mike Smith , Thomas David Rivers , drosih@rpi.edu, wjw@surf.IAE.nl, hackers@FreeBSD.ORG Subject: Re: Variant Link implementation, continued In-reply-to: Your message of "Fri, 03 Jul 1998 22:38:49 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Jul 1998 21:07:20 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 9:26 PM -0500 7/3/98, Mike Smith wrote: > >> > > >> > Then I'll be thinking about haveing 2 rules of resolution: > >> > @{....} > >> > and ${....} > >> > > >> > >> I don't mean to badger... but what if you, in an existing installation, > >> already have symlinks that contain that text? Won't adding this > >> facility break those existing links? > >> > >> [And, don't laugh, but I do have links and files that begin with '$', > >> and, even worse, have '$' embedded in the middle of them...] > > > >In the existing sample implementation, you would have to have links > >whose names comply explicitly with the syntax ...${}... where > >is a valid tag in the variant link namespace. > > > >I think that this is sufficiently unlikely given that there have been > >only two respondents that actually use '$' in names at all... > > How much trouble is this syntax going to cause since it looks just > like shell parameters and will have to be escaped just the right number > of times to get it passed through the shells? Wouldn't it be easier if > we avoid a syntax that the shell will alter? The point was to look _just_like_ the shell syntax, to avoid inventing Yet Another Syntax. Given that you already have to do all that magic for passing such text to other shells, this is an something that people already know and understand. We already have lots of diversity; no need to invent more complexity. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message