From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29310 invoked by alias); 29 Jun 2012 10:07:25 -0000 Received: (qmail 29296 invoked by uid 22791); 29 Jun 2012 10:07:23 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 Jun 2012 10:07:11 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53796] I/O INQUIRE of RECL: If not specified in OPEN, the default value should be returned (sequential access) Date: Fri, 29 Jun 2012 10:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-06/txt/msg01924.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796 --- Comment #5 from Tobias Burnus 2012-06-29 10:07:10 UTC --- (In reply to comment #4) > But Fortran doesn't have unsigned integers. If the intention is to indicate no > practical limit, then I guess the value to return is HUGE(0). And we should fill an interpretation request regarding this issue - as suggested by Richard Maine. Regarding the limit: I have to admit that I do not understand how GFORTRAN_DEFAULT_RECL is currently handled. Will it be the true upper bound, will it be extended etc.? There is a lot of special code, but that value seems to get only set for STDIN/STDOUT/STDERR. Additionally, using a special value from the allowed range askes (in principle) for trouble. Using a negative value internally for special values might make more sense - though it might require additional conditional checks (-> slower, potential sources for bugs).