Date: Wed, 07 May 2008 15:04:50 -0700 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Alfred Perlstein <alfred@FreeBSD.org> Cc: Peter Jeremy <peterjeremy@optushome.com.au>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, John Baldwin <jhb@FreeBSD.org>, cvs-src@FreeBSD.org Subject: Re: cvs commit: src/include stdio.h src/lib/libc/stdio clrerr.c feof.c ferror.c fileno.c getc.c getchar.c local.h putc.c putchar.c xprintf.c Message-ID: <48222782.7000303@FreeBSD.org> In-Reply-To: <20080507064013.GU32532@elvis.mu.org> References: <200805051603.m45G3rrN089219@repoman.freebsd.org> <200805051459.29200.jhb@freebsd.org> <20080505192417.GS7293@server.vk2pj.dyndns.org> <200805051637.43073.jhb@freebsd.org> <20080507064013.GU32532@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alfred Perlstein wrote: >> It appears that autoconf only believes a type is real if you can typedef it to >> another type, cast 0 to a valid pointer to the new typedef'd type, and do a >> sizeof() of the typdef'd type. The last is where having an opaque type >> breaks down for scripts that want to make sure FILE is a real type. > > > Oh c'mon! we're going to revert this needed fix just because of > autoconf? > > By the time 8.0 rolls around, autoconf will be fixed and there > will be some standard patch/workaround for old autoconf. > > Let's just roll forward with this. We've needed it for years. Can you please explain the "needed" part? What are gains apart from pure aesthetics and removing some type dependency from libc that otherwise needs to know actual storage type of pthread_t&Co? Neither is worth breaking zillion autoconf scripts out there IMHO (not everybody uses up to date ports and ports in general!). -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48222782.7000303>