public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53939] allows assignment to INTENT(IN) nested component Date: Thu, 12 Jul 2012 13:29:00 -0000 [thread overview] Message-ID: <bug-53939-4-LajwUsnSRj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53939-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53939 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-12 13:29:08 UTC --- (In reply to comment #1) > However, both "elem" and "cl2g" are pointers - thus the "intent(in)" doesn't > apply. [Or more precisely, for "cl2g" the intent doesn't apply at all (as it > is underneath a pointer component) while for "elem" it only applies to > pointer-association changes: Namely, pointer assignment and > allocate/deallocate/nullify of "cl2g" is prohibited due to intent(in), That "cl2g" should have been "elem" - sorry for the typo. > changing its value is allowed.]
next prev parent reply other threads:[~2012-07-12 13:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-12 12:28 [Bug fortran/53939] New: " Bil.Kleb at NASA dot gov 2012-07-12 13:24 ` [Bug fortran/53939] " burnus at gcc dot gnu.org 2012-07-12 13:29 ` burnus at gcc dot gnu.org [this message] 2012-07-12 13:32 ` Bil.Kleb at NASA dot gov
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=bug-53939-4-LajwUsnSRj@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).