From: "Laurynas Biveinis" Date: Wed, 11 Jul 2001 16:36:16 +0200 To: Eli Zaretskii Cc: djgpp-workers AT delorie DOT com Subject: Re: Comments on GCC 3.0 distribution Message-ID: <20010711163616.A291@lauras.lt> Mail-Followup-To: Eli Zaretskii , djgpp-workers AT delorie DOT com References: <20010710181253 DOT A472 AT lauras DOT lt> <1438-Tue10Jul2001222330+0300-eliz AT is DOT elta DOT co DOT il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1438-Tue10Jul2001222330+0300-eliz@is.elta.co.il> User-Agent: Mutt/1.3.18i 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 > Yes, we have lots of Posix _POSIX_* constants, and quite a few others. > I'm afraid that without out limits.h being included by the one which > comes with GCC, some programs which need those constants might not > compile. Another poor answer, but in this case it would be ``too bad to be true'' - too many broken platforms. > The problem is, again, with any program which compiled with our > stddef.h because it used some data type defined by sys/djtypes.h. It > could fail to compile with GCC's stddef.h. You mean that code like #include __dj_blah_t will stop working? Laurynas