public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/26891] Automatic conversion for optional parameters of missing dummies
Date: Tue, 28 Mar 2006 09:46:00 -0000	[thread overview]
Message-ID: <20060328094608.5383.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26891-10374@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from paulthomas2 at wanadoo dot fr  2006-03-28 09:46 -------
Subject: Re:  Automatic conversion for optional parameters
 of missing dummies

toon at moene dot indiv dot nluug dot nl wrote:

>------- Comment #1 from toon at moene dot indiv dot nluug dot nl  2006-03-28 08:15 -------
>  
>
>>   logical, optional, intent(in) :: back
>>   myscan = scan (str, substr, back)
>>    
>>
>
>I thought passing non-present optional arguments down to routines as an
>optional argument is within the confines of the Standard.
>
>If in doubt, consult comp.lang.fortran ...
>  
>
I would rather curl up in front of the fire with the standard - 
comp.lang.fortran comes with a population that seems excessively "up 
yours" on such matters.  I cannot be bothered with the aggression.

However, if you are right, that's great; I will spread the solution to 
all procedure calls.  Right now, I need to get out of this TRANSFER mess!

Best regards

Paul


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26891


  parent reply	other threads:[~2006-03-28  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 18:47 [Bug fortran/26891] New: " pault at gcc dot gnu dot org
2006-03-28  8:15 ` [Bug fortran/26891] " toon at moene dot indiv dot nluug dot nl
2006-03-28  9:46 ` paulthomas2 at wanadoo dot fr [this message]
2006-03-28 10:18 ` pault at gcc dot gnu dot org
2006-04-02 20:21 ` patchapp at dberlin dot org
2006-04-05  7:25 ` pinskia at gcc dot gnu dot org
2006-04-05 13:23 ` hjl at gcc dot gnu dot org
2006-04-07  6:02 ` pault at gcc dot gnu dot org
2006-04-07  6:03 ` pault at gcc dot gnu dot org
2006-04-12  1:22 ` pinskia 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=20060328094608.5383.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).