Date:	Fri, 29 Sep 2000 10:42:59 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT inter DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<8011-Fri29Sep2000104259+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5h
In-reply-to:	<8r0tfa$3oe$1@newsg2.svr.pol.co.uk>
	(matt AT the-good-stuff DOT freeserve DOT co DOT uk)
Subject:	Re: porting <dir.h> etc. to msvc
References:	<8qtjsd$78b$1 AT news5 DOT svr DOT pol DOT co DOT uk> <8qtti5$mpq$1 AT neptunium DOT btinternet DOT com> <8r0tfa$3oe$1 AT newsg2 DOT svr DOT pol DOT co DOT uk>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Matthew Smith" <matt AT the-good-stuff DOT freeserve DOT co DOT uk>
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 29 Sep 2000 03:12:55 +0100
> 
> I meant specifically the findfirst and findnext functions which work from
> ffblk structures.

Perhaps you could write MSVC-compatible FindFirst, FindNext and
FindClose, and donate them to DJGPP.  Then people could write DJGPP
programs that are portable to MSVC with minimal fuss.

(We do already have _dos_findfirst and _dos_findnext, but they are
compatible to 16-bit MSC compilers, and so don't support long file
names on Windows.)

> I would ideally like a file called dj.lib in my msdev/lib and versions of
> all the standard headers
> this would allow DJGPP programs to be compiled with minimal adaptation
> 
> I can see problems with inevitable name clashes and patching extra
> prototypes in existing .h files

Exactly.  The Right Way of writing portable programs is to use
portable features.  Compatibility libraries and headers don't work
well when you need them for system headers and standard library
functions.

- Raw text -