public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wchemelewski at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43158] No default integer descriptor width
Date: Wed, 24 Feb 2010 02:36:00 -0000 [thread overview]
Message-ID: <20100224023616.20623.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43158-18827@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from wchemelewski at gmail dot com 2010-02-24 02:36 -------
Thanks for being a dick, appreciated.(In reply to comment #1)
> (In reply to comment #0)
> > With the following code:
> >
> > INTEGER :: someint
> > CHARACTER (LEN=40) :: strcounter
> > WRITE(strcounter,'(I)') someint
> >
> > The error message is generated:
> >
> > WRITE(strcounter,'(I)') someint
> > 1
> > Error: Nonnegative width required in format string at (1)
> >
> > Which to me just suggests that gfortran does not have the (i believe) standard
> > behavior of automatically assigning a width to the format descriptor based on
> > the given integer. However, this only appears to be a problem when using a
> > character variable/internal file.
> >
>
> It suggests to me that you need to read a book on Fortran or
> the Standard. It also fails for writing to unit=6.
>
> laptop:kargl[207] gfortran44 -o z a.f90
> a.f90:2.11:
>
> write(*,'(I)') i
> 1
> Error: Nonnegative width required in format string at (1)
>
>
> You can get want you by using 'write(strcounter,*) someint'
> or 'write(strcounter,'(I0)') someint'.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43158
next prev parent reply other threads:[~2010-02-24 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 0:37 [Bug fortran/43158] New: " wchemelewski at gmail dot com
2010-02-24 2:33 ` [Bug fortran/43158] " kargl at gcc dot gnu dot org
2010-02-24 2:36 ` wchemelewski at gmail dot com [this message]
2010-02-24 2:43 ` kargl at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100224023616.20623.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).