Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20020508110758.0267eee8@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Wed, 08 May 2002 11:13:51 -0400
To: Mellman Thomas <Thomas DOT Mellman AT icn DOT siemens DOT de>,
   "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: RE: A proposal for a Cygnus naming convention
In-Reply-To: <BE684E2C997AD51199530002A56B20796C3654@MCHH2A1E>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:05 AM 5/8/2002, Mellman Thomas wrote:
> >>-----Original Message-----
> >>From: Gilgamesh Nootebos [mailto:Gilgamesh DOT Nootebos AT elegant DOT nl]
> >>Sent: Wednesday, May 08, 2002 4:56 PM
> >>To: cygwin AT cygwin DOT com
> >>Subject: Re: A proposal for a Cygnus naming convention
> >>
> >>
> >>Mellman Thomas wrote:
> >>> 
> >>> Okay, it's clear now that it won't be possible to keep 
> >>things easy to parse.
> >>> 
> >>This is almost trivially easy if I wanted to manipulate 
> >>mounts points in 
> >>a script:
> >>
> >>$ regtool -k list 'HKLM\software\Cygnus Solutions\Cygwin\mounts v2'
> >> >/
> >> >/usr/bin
> >> >/usr/lib
> >> >/home
> >>
> >>$ regtool get 'HKLM\software\Cygnus Solutions\Cygwin\mounts 
> >>v2\/home\native'
> >> >C:\Documents and Settings\gilgames\Mijn Documenten
> >>
> >>There is only one reason I might want to do this; with 
> >>mount(1) I can't 
> >>easily get exactly the string I want without falling back to 
> >>something 
> >>like sed/awk/perl/<add your favourite stream manipulation tool here>.
> >>
> >>And unices handle [[:space:]] characters very well, but it just isn't 
> >>tradition to use them.
>
>
>
>It's just that I like to use split() in perl or $1, $2, $3 in awk.  To say it's "easy" to handle blanks with Unix is ... well, to avoid anything that might inflame, let's say, academic.
>
>Incidently, I haven't heard anyone explain what purpose the blank in "mount v2" serves.


It "serves" no purpose.  It just is.  

OK, I think we get the point.  Spaces in any name make your life harder.  
You'd rather they don't exist.  Fine.  Whether I agree with that or not, 
they will persist.  We can all discourage them but they will appear.  And
ones that exist already aren't likely to change without a strong need.  
Unfortunately, I don't think ease of Perl programming is going to be the
clincher.  Sorry.  I guess you'll need to find a way to handle them for 
your needs.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/