From: "Laurynas Biveinis" <lauras AT softhome DOT net>
Date: Thu, 24 May 2001 20:05:58 +0200
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Add d_type member to struct dirent
Message-ID: <20010524200558.A285@lauras.lt>
Mail-Followup-To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	djgpp-workers AT delorie DOT com
References: <20010523214205 DOT A986 AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010524083434 DOT 17472D-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
In-Reply-To: <Pine.SUN.3.91.1010524083434.17472D-100000@is>; from eliz@is.elta.co.il on Thu, May 24, 2001 at 08:43:37AM +0300
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


> > Another note - please include src/libc/compat/unistd/xsymlink.h and replace
> > magic number with _SYMLINK_FILE_LEN from here, just in case.
> 
> Thanks for the tip.
> 
> How about moving it to some header in include/libc, then?  We normally 
> avoid including private headers in other directories (it gets in the way 
> when directory structure is changed).

There is libc/symlink.h, but I'm touchy about exposing such details
to users, so they could assume they can play with these details.
Ideally we could have src/libc/include for this stuff.

Laurynas