From maine@altair.dfrc.nasa.gov Wed Apr 3 22:43:47 1996 Received: from altair.dfrc.nasa.gov ([130.134.34.72]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id WAA04073 for ; Wed, 3 Apr 1996 22:43:44 +0200 Received: by altair.dfrc.nasa.gov (SMI-8.6/SMI-SVR4) id HAA05314; Wed, 3 Apr 1996 07:59:20 -0800 Date: Wed, 3 Apr 1996 07:59:20 -0800 Message-Id: <199604031559.HAA05314@altair.dfrc.nasa.gov> From: Richard Maine To: Craig.Dedo@mixcom.com CC: sc22wg5@dkuug.dk In-reply-to: <199604031346.PAA29872@dkuug.dk> (message from Craig Dedo on Wed, 03 Apr 96 07:43:08 -0600) Subject: Re: (SC22WG5.1057) Default Data Type - 2 Different Definitions? > we may have a problem with the term "default". In using the concept of > "default" kind of data type, we MAY actually be using two differing and > incompatible definitions. > 1. The "default" kind for a data type is the kind of the data type which > is the most frequent and suitable for the application which the programmer > is writing. > > 2. The "default" kind for a data type is the kind of data type which is > most natural for the hardware architecture which the Fortran compiler is > compiling source code for. > we should clearly define both usages of the concept of default kind and > rigorously distinguish which one we are using in any given situation. We are using neither one. The default kind is the one that the compiler uses when some other kind is not specified. It has little to do with what is most natural and suitable for anything. (Of course, it seems likely that a vendor would strive to make it both suitable for applications and natural for the architecture, but neither of these has much obvious to do with the standard). -- Richard Maine maine@altair.dfrc.nasa.gov