Date:	Mon, 10 Feb 2003 12:06:42 -0500
Message-Id:	<200302101706.h1AH6g803162@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp-workers AT delorie DOT com
In-reply-to:	<3E47B9E6.29472.C3BDC5DE@localhost> (cyp@fb14.uni-mainz.de)
Subject:	Re: fix for copyrite.c[c]/copyrite.pl
References:	<3E450FB4 DOT 28479 DOT B954E177 AT localhost> from "Cyrus Patel" at Feb 08, 2003 02:08:34 PM <3E47B9E6 DOT 29472 DOT C3BDC5DE AT localhost>
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

Why did you change the file from C++ to C?  That should be necessary.

> b) as described below, I'm into error checking, and djgpp glob()
> doesn't support an error handler.

Er, it should.

> I wanted to build the executable with turboc and watcomc too

Don't forget linux.

> a) do_file() uses fd io rather than stream io - its more efficient,
>    its easier to check for errors, and its immune to binary/text
>    differences.

No, it's not immune.  It has exactly the same issues as stream io.
And stream io is specifically designed to be much more efficient than
raw io in a djgpp environment.  Please use stream io.

> Are we talking about the same file? :)

Don't be sarcastic.  What he means is that it would be nice to have
something in the utils.txi file that properly documents what the
utility is and how to properly use it.  Just because it wasn't done
before doesn't mean it shouldn't be done now.

- Raw text -