Tobias Burnus - Re: [patch, fortran, committed] Document COMPLEX*k syntax quirk. (original) (raw)

This is the mail archive of the gcc-patches@gcc.gnu.orgmailing list for the GCC project.

• From: Tobias Burnus
• To: Brooks Moses
• Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
• Date: Fri, 23 Feb 2007 10:44:02 +0100
• Subject: Re: [patch, fortran, committed] Document COMPLEX*k syntax quirk.
• References: <45DE081E.2070902@codesourcery.com> <45DE0C37.5060802@net-b.de> <45DE15BF.3000909@codesourcery.com> <45DE19D3.6060408@codesourcery.com>

Hi Brooks,

Brooks Moses wrote:

On second thought, you're right. It doesn't hurt to be explicit about this. How about this version? I like it. It not only states in how far COMPLEX is different, but also why.

Does the comment need to clarify that? If so, I can try to make it clearer. Specifically, how about: /* Match an extended-f77 "TYPESPEC*bytesize"-style kind specification. This assumes that the byte size is equal to the kind number for non-COMPLEX types, and equal to twice the kind number for COMPLEX. */ I think this is clearer.

Thanks for updating the documentation (in general).

Tobias

• References:
  • [patch, fortran, committed] Document COMPLEX*k syntax quirk.
    * From: Brooks Moses
  • Re: [patch, fortran, committed] Document COMPLEX*k syntax quirk.
    * From: Tobias Burnus
  • Re: [patch, fortran, committed] Document COMPLEX*k syntax quirk.
    * From: Brooks Moses
  • Re: [patch, fortran, committed] Document COMPLEX*k syntax quirk.
    * From: Brooks Moses