From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32007 invoked by alias); 12 Apr 2005 13:18:52 -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 31985 invoked by uid 48); 12 Apr 2005 13:18:48 -0000 Date: Tue, 12 Apr 2005 13:18:00 -0000 Message-ID: <20050412131848.31983.qmail@sourceware.org> From: "tow21 at cam dot ac dot uk" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050216120130.20006.tow21@cam.ac.uk> References: <20050216120130.20006.tow21@cam.ac.uk> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug fortran/20006] $ format extension doesn't work X-Bugzilla-Reason: CC X-SW-Source: 2005-04/txt/msg01549.txt.bz2 List-Id: ------- Additional Comments From tow21 at cam dot ac dot uk 2005-04-12 13:18 ------- (In reply to comment #4) > OK. I have a patch to make $ work, I'll add a warning when this is possible at > compile-time (I don't think we want to have a warning at runtime, especially > since there is general agreement on this extension). As an extension, that's fine. But if I've compiled with -pedantic -std=f95, then I'd expect an error where possible at compile-time, and a fatal IO error at runtime. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20006