Sender:	tim AT riker DOT skynet DOT be
Message-ID:	<3B7BA678.C6644C6D@falconsoft.be>
Date:	Thu, 16 Aug 2001 12:54:48 +0200
From:	Tim Van Holder <tim DOT vanholder AT falconsoft DOT be>
Organization:	Anubex N.V.
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.16-3 i686)
X-Accept-Language:	en, nl-BE, nl
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
CC:	matt AT the-good-stuff DOT freeserve DOT co DOT uk
Subject:	Re: porting DJGPP libs to other compilers
References:	<009801c123df$58317540$0101bfbf AT f9c6f0> <200108131245 DOT IAA19039 AT envy DOT delorie DOT com>
Reply-To:	djgpp AT delorie DOT com

DJ Delorie wrote:
> 
> > a) To support the filefirst() filenext() and fileclose() functions
> > with the ffblk structure filled to the best of each O/Ses ability.
> >
> > b) The extra string functions which are not POSIX compliant, yet depended on
> > by many, would be packaged for other compilers.
> 
> Have you checked out libiberty?

That would be my suggestion as well - libiberty already has
implementations of many functions that are missing on broken on some
systems.  You should consider submitting code to them instead of
starting your own project (plus, since libiberty is a GNU project and
part of major distributions like gcc, binutils and gdb, it's more likely
that its code will be refined and tinkered with).
If the libiberty maintainers should decide that it's not useful to add
portable implementations of findfirst et al to libiberty, then you could
of course start your own library (perhaps named libnobill?).

-- 
Tim Van Holder - Anubex N.V.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message was posted using plain text. I do not endorse any
products or services that may be hyperlinked to this message.

- Raw text -