Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Thu, 22 Feb 2001 17:18:02 -0600 (CST) From: Mumit Khan To: "J. J. Farrell" cc: Cygwin Mailing List Subject: Re: mingwin: dirent structure d_name field is pointer not array In-Reply-To: <200102222240.f1MMeA708837@capella.ssd.hal.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 22 Feb 2001, J. J. Farrell wrote: > SUS 2 and predecessors define d_name as rather > than . I can't think of any reasonable code which would > care about the difference though, especially since the length > of the string is greater than the declared size of the array in > some implementations anyway. I agree that it should be char[], not char *, and that's something we will fix. As far as the C and C++ language semantics go, it should make no difference in the usage however. > I agree that it's technically wrong if it's defined as a , > but I'd be interested if Reuben could give an illustration of why > it matters. I'd be interested as well. This should be in mingw mailing list, not Cygwin. I do apologize for polluting Cygwin list with this rather off-topic post. Regards, Mumit -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple