From Keith.Bierman@Eng.Sun.COM Wed Apr 17 23:48:02 1996 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id XAA24022 for ; Wed, 17 Apr 1996 23:47:59 +0200 Received: by mercury.Sun.COM (Sun.COM) id OAA06313; Wed, 17 Apr 1996 14:46:47 -0700 Received: from chiba.eng.sun.com by Eng.Sun.COM (5.x/SMI-5.3) id AA04564; Wed, 17 Apr 1996 14:46:42 -0700 Received: from chiba (localhost) by chiba.eng.sun.com (5.x/SMI-SVR4) id AA14641; Wed, 17 Apr 1996 14:46:41 -0700 Message-Id: <9604172146.AA14641@chiba.eng.sun.com> To: bleikamp@mozart.convex.com (Richard Bleikamp) Cc: Craig.Dedo@mixcom.com (Craig Dedo), sc22wg5@dkuug.dk Subject: Re: (SC22WG5.1068) Question on Implementation Benefits of Fortran POINTER Feature In-Reply-To: Your message of "Wed, 17 Apr 1996 15:53:19 CDT." <199604172055.WAA23613@dkuug.dk> Date: Wed, 17 Apr 1996 14:46:41 -0700 From: Keith Bierman QED Fine response. But >Mostly those described above. In addition, the "type safeness" of Fortran >pointers allows more alias analysis than "old" C, although I think ANSI C >may have addressed some of this, particularly with restricted pointers. ANSI C doesn't have restricted pointers. The ANSI C to come will probably have them; but it isn't a DIS yet ;>