Date: Mon, 9 Jul 2001 11:14:26 +0200 (MET DST)
From: Alexander Supalov <Alexander.Supalov@XXXXXXXXXX>
Subject: redefining MPI_LONG_LONG_INT
To: mpi-21@XXXXXXXXXXXXX
Cc: hans-christian.hoppe@XXXXXXXXXX,georg.bisseling@XXXXXXXXXX
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 7hy8zCZf+LMg83k7m6+SIA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 i86pc i386 
Sender: owner-mpi-21@XXXXXXXXXXXXX
Precedence: bulk
Reply-To: mpi-21@XXXXXXXXXXXXX

Hi everybody,

It's just stricken my eye that the MPI_LONG_LONG_INT as voted in last time 
conflicts with the usual meaning of the MPI_type_INT constants. Those are 
normally used to indicate a <type,MPI_INT> pair suitable for the MPI_MINLOC and 
MPI_MAXLOC reduction operations.

From this point of view, the now affirmed equivalence of the MPI_LONG_LONG_INT 
and MPI_LONG_LONG (item 16 of the 1st bunch) looks fairly unfortunate, doesn't 
it?

I think that it's better to roll this particular change back and reintroduce the 
MPI_LONG_LONG_INT (if need be) consistently with the rest of the standard.

Best regards.

Alexander
 
// pallas  GmbH  ............  Dr Alexander Supalov .....
   Hermuelheimer Str. 10       Software Engineer
   D-50321 Bruehl, Germany     supalov@XXXXXXXXXX           
   fax +49-(0)2232-1896-29     phone  +49-(0)2232-1896-0 
   http://www.pallas.com       direct +49-(0)2232-1896-34
.........................................................