From: Wu Zhou <woodzltc@cn.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA]: Fix a comment typo in expression.h
Date: Tue, 07 Jun 2005 09:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0506071707190.28024@plinuxt18.cn.ibm.com> (raw)
I found a typo when reading the source of expression.h. OK to commit?
Thanks.
2005-06-07 Wu Zhou <woodzltc@cn.ibm.com>
* expression.h (enum exp_opcode): Fix a comment typo.
Index: expression.h
===================================================================
RCS file: /cvs/src/src/gdb/expression.h,v
retrieving revision 1.14
diff -c -p -r1.14 expression.h
*** expression.h 10 Apr 2004 22:10:00 -0000 1.14
--- expression.h 7 Jun 2005 09:10:03 -0000
*************** enum exp_opcode
*** 192,198 ****
/* This is EXACTLY like OP_FUNCALL but is semantically different.
In F77, array subscript expressions, substring expressions
and function calls are all exactly the same syntactically. They may
! only be dismabiguated at runtime. Thus this operator, which
indicates that we have found something of the form <name> ( <stuff> ) */
OP_F77_UNDETERMINED_ARGLIST,
--- 192,198 ----
/* This is EXACTLY like OP_FUNCALL but is semantically different.
In F77, array subscript expressions, substring expressions
and function calls are all exactly the same syntactically. They may
! only be disambiguated at runtime. Thus this operator, which
indicates that we have found something of the form <name> ( <stuff> ) */
OP_F77_UNDETERMINED_ARGLIST,
next reply other threads:[~2005-06-07 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 9:21 Wu Zhou [this message]
2005-06-07 13:15 ` Daniel Jacobowitz
2005-06-08 6:41 ` Wu Zhou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0506071707190.28024@plinuxt18.cn.ibm.com \
--to=woodzltc@cn.ibm.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox