This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: fortran/26041: FORTRAN compiler won't compile the valid code
- From: Paul Brook <paul at codesourcery dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Paul Thomas <paulthomas2 at wanadoo dot fr>, "H. J. Lu" <hjl at lucon dot org>, fortran at gcc dot gnu dot org
- Date: Thu, 2 Feb 2006 19:09:55 +0000
- Subject: Re: PATCH: fortran/26041: FORTRAN compiler won't compile the valid code
- References: <20060131235212.GA16716@lucon.org> <20060202011740.GA929@lucon.org> <43E24A68.8030301@wanadoo.fr>
> >???????* resolve.c (gfc_resolve_type): New function.
> >???????(gfc_resolve_code): Likewise.
> >???????(gfc_resolve): Use them.
>
> Please be a little bit more descriptive; A sentence for each on what the
> new functions do and what was done to gfc_resolve will be enough. eg.:
Just "New function" is fine.
Quoting from the GNU coding standards
http://www.gnu.org/prep/standards/html_node/Change-Log-Concepts.html#Change-Log-Concepts
"For example, 'New function' is enough for the change log when you add a
function, because there should be a comment before the function definition to
explain what it does."