(j3.2006) (SC22WG5.5438) RE: Proposal of a new requirement : CMDMSG optional argument in 3 subroutines

[Craig Dedo CAPM]

Everyone:

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

 

            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?m surprised someone didn?t bring this up earlier.  Is it possible
to fit this into the development schedule for Fortran 2015?

 

            What do other think about:

            (1) The merit of the idea.

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

 

            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                         Mobile Phone:  (414) 412-5869

Brookfield, WI   53008-0423    E-mail:  < <mailto:craig at ctdedo.com> craig at ctdedo.com>

USA

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

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

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

> On Behalf Of Bernard PICHON

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

> To: sc22wg5 at 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=

> for I/O routines, keyword ERRMSG= 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 !!

> 

> ==================================================

> ===================================

> 

> 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.

> 

> ==================================================

> ====================================

> 

> Dr. Bernard PICHON (from France)

> CNRS ? Observatoire de la C?te d?Azur (OCA)

> 

> 

> _______________________________________________

> J3 mailing list

>  <mailto:J3 at mailman.j3-fortran.org> J3 at mailman.j3-fortran.org

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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.j3-fortran.org/pipermail/j3/attachments/20150127/c4a84f95/attachment.html