From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Tue Jan 27 18:41:36 2015 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 491163582C4; Tue, 27 Jan 2015 18:41:36 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 336 seconds by postgrey-1.34 at www5.open-std.org; Tue, 27 Jan 2015 18:41:35 CET Received: from atl4mhfb01.myregisteredsite.com (atl4mhfb01.myregisteredsite.com [209.17.115.55]) by www.open-std.org (Postfix) with ESMTP id 88CB6356F4B for ; Tue, 27 Jan 2015 18:41:34 +0100 (CET) Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by atl4mhfb01.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t0RHZxZH012831 for ; Tue, 27 Jan 2015 12:35:59 -0500 Received: from mailpod1.hostingplatform.com (atl4obmail05pod1.mgt.hosting.qts.netsol.com [10.30.71.117]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t0RHZmb1011530 for ; Tue, 27 Jan 2015 12:35:48 -0500 Received: (qmail 30596 invoked by uid 0); 27 Jan 2015 17:35:48 -0000 X-TCPREMOTEIP: 65.31.136.202 X-Authenticated-UID: craig@ctdedo.com Received: from unknown (HELO Telcontar) (craig@ctdedo.com@65.31.136.202) by 0 with ESMTPA; 27 Jan 2015 17:35:48 -0000 From: "Craig Dedo CAPM" To: "WG5 Mailing List" References: <20150127125841.B08CB3570D2@www.open-std.org> In-Reply-To: <20150127125841.B08CB3570D2@www.open-std.org> Subject: RE: (j3.2006) (SC22WG5.5437) Proposal of a new requirement : CMDMSG optional argument in 3 subroutines Date: Tue, 27 Jan 2015 11:35:21 -0600 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_044F_01D03A25.557D2450" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdA1iwTODoN7NQxgQBG+FtQe0FuIxQACMYVwASc5xFAACYtncA== Content-Language: en-us Sender: owner-sc22wg5@open-std.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_044F_01D03A25.557D2450 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Everyone: Bernard, thank you very much for bringing this idea to = everyone on the WG5 Mailing List. =20 I think this is a great idea. It would be very helpful to = have the command message text available in these three subroutines, just as it is = available in Execute_Command_Line. I=92m surprised someone didn=92t bring this up = earlier. Is it possible to fit this into the development schedule for Fortran 2015? =20 What do other think about: (1) The merit of the idea. (2) The ability to fit this into the development schedule of = Fortran 2015. =20 Please feel free to contact me at any time with any = questions or concerns that you may have. I am looking forward to hearing from you soon. =20 Sincerely, Craig T. Dedo, CAPM 17130 W. Burleigh Place P. O. Box 423 Mobile Phone: (414) 412-5869 Brookfield, WI 53008-0423 E-mail: < = craig@ctdedo.com> USA Linked-In: = http://www.linkedin.com/in/craigdedo > -----Original Message----- > From: j3-bounces@mailman.j3-fortran.org = [mailto:j3-bounces@mailman.j3-fortran.org] > On Behalf Of Bernard PICHON > Sent: Tuesday, January 27, 2015 06:58 > To: sc22wg5@open-std.org > Subject: (j3.2006) (SC22WG5.5437) Proposal of a new requirement : = CMDMSG optional > argument in 3 subroutines >=20 > Dear all members of WG5 >=20 > In the past I suggested to introduce in Fortran some means to retrieve = =93error > message=94 from the processor. This feature is now standardized with = keywords IOMSG=3D > for I/O routines, keyword ERRMSG=3D for memory and image control = routines and the > optional argument CMDMSG is defined in EXECUTE_COMMAND_LINE = subroutine. >=20 > I encounter these days some difficulties with the subroutine > GET_ENVIRONMENT_VARIABLE and discovered that this subroutine doesn=92t = implement any > means to retrieve =93error message=94 from the host processor although = the optional > argument STATUS is defined. >=20 > So, I put to WG5 the following requirement written by analogy with > EXECUTE_COMMAND_LINE subroutine : >=20 > Note that you may receive this mail twice due to a change in my mail = address ; > sorry for that !! >=20 > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Add the optional argument CMDMSG in subroutines GET_COMMAND , = GET_COMMAND_ARGUMENT > and GET_ENVIRONMENT_VARIABLE with this edit : >=20 > CMDMSG (optional) shall be a default character scalar. It is an INTENT = (INOUT) > argument. If an error condition occurs, it is assigned a = processor-dependent > explanatory message. > Otherwise, it is unchanged. >=20 > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Dr. Bernard PICHON (from France) > CNRS =96 Observatoire de la C=F4te d=92Azur (OCA) >=20 >=20 > _______________________________________________ > J3 mailing list > J3@mailman.j3-fortran.org > http://mailman.j3-fortran.org/mailman/listinfo/j3 =20 ------=_NextPart_000_044F_01D03A25.557D2450 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Everyone:

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Bernard, thank = you very much for bringing this idea to everyone on the WG5 Mailing = List.

 

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 I think this is a = great idea.=A0 It would be very helpful to have the command message text = available in these three subroutines, just as it is available in = Execute_Command_Line.=A0 I’m surprised someone didn’t bring = this up earlier.=A0 Is it possible to fit this into the development = schedule for Fortran 2015?

 

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 What do other = think about:

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 (1) The merit of = the idea.

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 (2) The ability = to fit this into the development schedule of Fortran = 2015.

 

        &nbs= p;   Please feel free to contact me at any time with any = questions or concerns that you may have.  I am looking forward to = hearing from you soon.

 

Sincerely,

Craig T. Dedo, = CAPM

17130 W. Burleigh Place

P. O. Box = 423           &nbs= p;            = ; Mobile Phone:  (414) 412-5869

Brookfield, WI   = 53008-0423    E-mail:  <craig@ctdedo.com>

USA

Linked-In:  http://www.linkedin.com/in/craigdedo=

> = -----Original Message-----

> = From: j3-bounces@mailman.j3-fortran.org = [mailto:j3-bounces@mailman.j3-fortran.org]

> = On Behalf Of Bernard PICHON

> = Sent: Tuesday, January 27, 2015 06:58

> = To: sc22wg5@open-std.org

> = Subject: (j3.2006) (SC22WG5.5437) Proposal of a new requirement : CMDMSG = optional

> = argument in 3 subroutines

> =

> = Dear all members of WG5

> =

> = In the past I suggested to introduce in Fortran some means to retrieve = “error

> = message” from the processor. This feature is now standardized with = keywords IOMSG=3D

> = for I/O routines, keyword ERRMSG=3D for memory and image control = routines and the

> = optional argument CMDMSG is defined in EXECUTE_COMMAND_LINE = subroutine.

> =

> = I encounter these days some difficulties with the = subroutine

> = GET_ENVIRONMENT_VARIABLE and discovered that this subroutine = doesn’t implement any

> = means to retrieve “error message” from the host processor = although the optional

> = argument STATUS is defined.

> =

> = So, I put to WG5 the following requirement written by analogy = with

> = EXECUTE_COMMAND_LINE subroutine :

> =

> = Note that you may receive this mail twice due to a change in my mail = address ;

> = sorry for that !!

> =

> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> =

> = Add the optional argument CMDMSG in subroutines GET_COMMAND , = GET_COMMAND_ARGUMENT

> = and GET_ENVIRONMENT_VARIABLE with this edit :

> =

> = CMDMSG (optional) shall be a default character scalar. It is an INTENT = (INOUT)

> = argument. If an error condition occurs, it is assigned a = processor-dependent

> = explanatory message.

> = Otherwise, it is unchanged.

> =

> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> =

> = Dr. Bernard PICHON (from France)

> = CNRS – Observatoire de la C=F4te d’Azur = (OCA)

> =

> =

> = _______________________________________________

> = J3 mailing list

> = J3@mailman.j3-fortran.org=

> = http://mailman.j3-fortran= .org/mailman/listinfo/j3

 

------=_NextPart_000_044F_01D03A25.557D2450--