Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: From: Mellman Thomas To: "'Robert Collins'" , Mellman Thomas , cygwin@cygwin.com Subject: RE: A proposal for a Cygnus naming convention Date: Wed, 8 May 2002 17:16:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" >>-----Original Message----- >>From: Robert Collins [mailto:robert.collins@itdomain.com.au] >>Sent: Wednesday, May 08, 2002 5:11 PM >>To: Mellman Thomas; cygwin@cygwin.com >>Subject: RE: A proposal for a Cygnus naming convention >> >> >> >> >>> -----Original Message----- >>> From: Mellman Thomas [mailto:Thomas.Mellman@icn.siemens.de] >>> Sent: Thursday, May 09, 2002 1:06 AM >> >> >>> 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's easier to read than "mountv2". Could be. How about mount_v2? >> Plus it confuses perl programs. Hey! I used to hate perl too until I had to study a good perl program. The thing about perl (not to go off-topic, or anything), is that it's the only interpretive language that I know of (except for Java, which I don't know very well) which has both 1) structured data and 2) pointer-optimized accesses. So there! -- 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/