From: ebachalo AT cygnus DOT com (Eric Bachalo)
Subject: Re: -@file
1 Apr 1998 11:56:37 -0800
Message-ID: <3.0.5.32.19980401111835.0092ed20.cygnus.cygwin32.developers@pop.cygnus.com>
References: <m167ktsggy DOT fsf AT creche DOT cygnus DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: tromey AT cygnus DOT com
Cc: Ian Lance Taylor <ian AT cygnus DOT com>, cygwin32-developers AT cygnus DOT com,
        fgeers AT cygnus DOT com

At 08:34 AM 4/1/98 -0700, Tom Tromey wrote:
>Eric> I did it on purpose because I thought is might be useful to be
>Eric> able to stick long quoted strings in a file.  Don't know of any
>Eric> instance one needs a long or often used quote in a command line
>Eric> though.
>
>Command-line parsing/dequoting is done after the file is read.  So you
>can put a long quoted string into a file by putting the quotes in the
>file.

Agreed, but if someone wanted to put multiple files in one set of quotes
they could by " -@intro -@body -@conclude " .  Although I can not imagine a
need for this.  Its pretty hard to defend how I wrote it when it really
doesn't matter that much to me whether it respects quotes or not. :)

>
>I guess it doesn't matter to me all that much.  Odds are I will never
>encounter this feature in practice.

For now I will leave it out just because it is less lines of code.  I would
not be offended if someone went in and changed the logic just as long as
they keep documentation (Frederick Geers) informed.


Best Regards,

Eric Bachalo