From owner-cvs-all  Mon Jul  2 17:13:51 2001
Delivered-To: cvs-all@freebsd.org
Received: from sneakerz.org (sneakerz.org [216.33.66.254])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3488D37B401; Mon,  2 Jul 2001 17:13:43 -0700 (PDT)
	(envelope-from bright@sneakerz.org)
Received: by sneakerz.org (Postfix, from userid 1092)
	id C4F805D010; Mon,  2 Jul 2001 19:13:42 -0500 (CDT)
Date: Mon, 2 Jul 2001 19:13:42 -0500
From: Alfred Perlstein <bright@sneakerz.org>
To: Dima Dorfman <dima@unixfreak.org>
Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sbin/mountd mountd.c
Message-ID: <20010702191342.Y84523@sneakerz.org>
References: <20010702185739.X84523@sneakerz.org> <20010703000646.13F1A3E28@bazooka.unixfreak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20010703000646.13F1A3E28@bazooka.unixfreak.org>; from dima@unixfreak.org on Mon, Jul 02, 2001 at 05:06:45PM -0700
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

* Dima Dorfman <dima@unixfreak.org> [010702 19:06] wrote:
> Alfred Perlstein <bright@sneakerz.org> writes:
> > * Dima Dorfman <dd@FreeBSD.org> [010702 18:56] wrote:
> > > dd          2001/07/02 16:56:01 PDT
> > > 
> > >   Modified files:
> > >     sbin/mountd          mountd.c 
> > >   Log:
> > >   Correct handling of continuation lines.  Instead of treating the
> > >   backslash as nothing, treat it like a space so that adjacent lines
> > >   aren't glued together.
> > 
> > So now how does one use a backslash when one doesn't want a space?
> 
> Where would you want to use a backslash?  AFAIK there are no
> parameters in exports(5) where a backslash would be valid.  If you're
> talking about using it in the middle of a word and at the end of the
> line, like this:
> 
> 	/usr -alldirs -netw\
> 	ork=fish host1 host2
> 
> then this commit puts you out of luck.  However, I honestly don't see
> why somebody would want to do that.  The new sematic is much more
> intuitive and in line with most (every?) other file format that
> supports continuation lines.  I think it's what most people would
> expect when they use a backslash at the end of a line.

#include <stdio.h>

int main()
{

        printf("foo\
bar\n");
        return 1;
}

It doesn't matter much, but I wanted to see if you realized that.

-- 
-Alfred Perlstein [alfred@freebsd.org]
Ok, who wrote this damn function called '??'?
And why do my programs keep crashing in it?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message