From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 678 invoked by alias); 18 Jul 2005 15:01:12 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 664 invoked by uid 48); 18 Jul 2005 15:01:09 -0000 Date: Mon, 18 Jul 2005 15:02:00 -0000 Message-ID: <20050718150109.663.qmail@sourceware.org> From: "ralfixx at gmx dot de" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050429155408.21286.ralfixx@gmx.de> References: <20050429155408.21286.ralfixx@gmx.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/21286] [4.0/4.1 Regression] filebuf::xsgetn vs pipes X-Bugzilla-Reason: CC X-SW-Source: 2005-07/txt/msg02233.txt.bz2 List-Id: ------- Additional Comments From ralfixx at gmx dot de 2005-07-18 15:01 ------- > portable C++ code using pipes has better being very very > careful with short reads, because the current Standard is > way too vague in this area I prefer C++ for the abstractions it allows. Having to code my I/O with the type of the underlying data stream type in mind defeats this abstraction to a great deal... > By the way, I would suggest pronouncing "broken" using the same > intonation of Martin Landau's Bela Lugosi in Ed Wood: > "Beware, beware... broken, broken..." ;) Let's pronounce it [kəˈpʊt] then :-) http://en.wiktionary.org/wiki/Kaput -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21286