Date: Mon, 26 Feb 2001 17:41:00 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Bruno Haible <haible AT ilog DOT fr>
cc: ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De, djgpp-workers AT delorie DOT com
Subject: Re: DJGPP specific patch for libiconv-1.5.1
In-Reply-To: <15002.30141.286268.122919@honolulu.ilog.fr>
Message-ID: <Pine.SUN.3.91.1010226173856.24373H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 26 Feb 2001, Bruno Haible wrote:

> Eli Zaretskii writes:
> 
> > why is the --binary option needed at all?  In other words, under what 
> > circumstances is the user expected to use --binary?
> 
> If he wants to use 'iconv' in a testsuite and compare the resulting
> output with the one he got on a Unix host.

If that's the only reason, then I'd recommend to remove that option.  
Text files on DOS/Windows should be compared with Diff, not with Cmp.

It is IMHO bad to have platform-specific options.  This is only justified 
if the program will be crippled without those options in some way.  Based 
on your description, this doesn't sound like such a case.