<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div class="BodyFragment"><font size="2"><span style="font-size:10pt;">
<div class="PlainText">Ok, here's a final copy -- see the new section in the Deprecated Interfaces chapter.<br>
<br>
I'll make a ticket for this, and send it to the mpi-forum list so that we're well-ahead of the T-2 week notice.<br>
<br>
</div>
</span></font></div>
<div class="BodyFragment"><font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
<br>
<br>
On Feb 4, 2014, at 3:31 AM, Rolf Rabenseifner <rabenseifner@hlrs.de> wrote:<br>
<br>
> Perfect.<br>
> <br>
> ----- Original Message -----<br>
>> From: "Jeff Squyres (jsquyres)" <jsquyres@cisco.com><br>
>> To: "MPI-WG Fortran working group" <mpiwg-fortran@lists.mpi-forum.org><br>
>> Sent: Tuesday, February 4, 2014 12:10:03 AM<br>
>> Subject: Re: [MPIWG Fortran] Draft chapter for discussion today<br>
>> <br>
>> On Feb 3, 2014, at 4:02 AM, Rolf Rabenseifner <rabenseifner@hlrs.de><br>
>> wrote:<br>
>> <br>
>>>> If Chapter 15 is to be renamed, I would agree that 17.1.4 should<br>
>>>> move. But I'm not sure this is a good idea.<br>
>>> <br>
>>> We used already in MPI-2.2 the "Chapter 15. Deprecated Functions"<br>
>>> in the general way "Deprecated Interfaces" when we added<br>
>>> the total C++ bindings to this chapter, i.e. all C++ constants,<br>
>>> functions, ,... .<br>
>> <br>
>> This is a good point.<br>
>> <br>
>>> To make the life easy, we should rename Chapter 15 into<br>
>>> "Chapter 15. Deprecated Interfaces". This would be consistent to<br>
>>> "Chapter 16. Removed Interfaces".<br>
>>> The normal text (i.e., text outside of Chap. 15+16) should<br>
>>> include as few deprecated features as possible.<br>
>> <br>
>> I see in MPI-2.2 chapter 15 a very brief blurb about how the C++<br>
>> bindings are deprecated. We then also put "deprecated" next to<br>
>> every binding throughout the text (and a few other select places,<br>
>> IIRC).<br>
>> <br>
>> So for mpif.h/MPI-4, I propose a compromise:<br>
>> <br>
>> 1. Rename chapter 15 as you suggest.<br>
>> <br>
>> 2. Put a brief blurb in 15 saying that mpif.h is deprecated, similar<br>
>> to what we did for C++ in MPI-2.2. I.e., do not move 17.1.4 or<br>
>> other giant blocks of text to chapter 15.<br>
>> <br>
>> --<br>
>> Jeff Squyres<br>
>> jsquyres@cisco.com<br>
>> For corporate legal information go to:<br>
>> <a href="http://www.cisco.com/web/about/doing_business/legal/cri/">http://www.cisco.com/web/about/doing_business/legal/cri/</a><br>
>> <br>
>> _______________________________________________<br>
>> mpiwg-fortran mailing list<br>
>> mpiwg-fortran@lists.mpi-forum.org<br>
>> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</a><br>
>> <br>
> <br>
> -- <br>
> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner@hlrs.de<br>
> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530<br>
> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832<br>
> Head of Dpmt Parallel Computing . . . <a href="http://www.hlrs.de/people/rabenseifner">
www.hlrs.de/people/rabenseifner</a><br>
> Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)<br>
> _______________________________________________<br>
> mpiwg-fortran mailing list<br>
> mpiwg-fortran@lists.mpi-forum.org<br>
> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</a><br>
<br>
<br>
-- <br>
Jeff Squyres<br>
jsquyres@cisco.com<br>
For corporate legal information go to: <a href="http://www.cisco.com/web/about/doing_business/legal/cri/">
http://www.cisco.com/web/about/doing_business/legal/cri/</a><br>
<br>
</div>
</span></font></div>
</body>
</html>