Message-Id: <200006141536.LAA31954@qnx.com> Subject: Re: tmpfile in DJGPP To: djgpp-workers AT delorie DOT com Date: Wed, 14 Jun 2000 11:36:32 -0400 (EDT) From: "Alain Magloire" In-Reply-To: from "Eli Zaretskii" at Jun 14, 2000 12:17:57 PM X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Bonjour > On Tue, 13 Jun 2000, Alain Magloire wrote: > > > When I write code that will be run on different platforms, > > I write it with "portability" in mind, so doing fflush(stdin) > > is not "portable". > > Even if a certain behavior is defined by a standard, it still makes > sense to refrain from using some features which are known to be broken > on some platforms. The feature we are discussing is IMHO one such > case. > > In other words, the standard is not the issue here; the issue is what > standard features should better not be used because not every platform > can support it, no matter how hard does it try to be Posix-compliant. > > After all, standards are supposed to help portability, and > portability is NOT defined to apply only to platforms which are 100% > compliant to the standard. If an important platfrom does not support > some feature required by a standard, then portability dictates that > this feature be avoided. > > I believe that many GNU programs already include special provisions > for known deficiencies of otherwise Posix-compliant platforms. I'm > arguing that this is one more case. > Points well taken. And for the other post, about the visibility of DJGPP within GNU/FSF, unfortunately I do not make the policies, but I will make a mental note if the subject comes in any discussion with RMS. The only thing I can do is to make provisions and accepts with an open mind some of the tweakings/patches for DJGPP, for the things I maintained. I can not speak for other maintainers. But you have to understand, for many people, some of the restrictions are quite "silly" and DOS is considered obsolete. So far what I've seen from browsing time to time this list, is that You guys are moving on and ready to port DJGPP to Win95,98,2000 Which makes it interesting. v203 is quite stable for DOS, but not so for Win,...,2000 What not for v204,v205 take full feature of Win,..2000 and if you really want to keep DOS make two distributions, with different compilation flags etc .. Just an idea, I have no idea what's involve. It just seem, for an outsider, that DJGPP is evolving by trying to follow ANSI C99, POSIX etc ... but does not take(or can not take) full advantage of Win9X,2000 -- au revoir, alain ---- Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!