Previous mail
Next mail
Formatted
Overview 10 days
Subject
Date
Thread
Author
From gpc-owner@gnu.de Tue Feb 18 06:54:25 2003
Received: from mail.ncifcrf.gov ([129.43.100.100])
by adele.gerwinski.de with esmtp (Exim 3.35 #1 (Debian))
id 18l0hw-0006zs-00
for <gpc@gnu.de>; Tue, 18 Feb 2003 06:54:20 +0100
Received: from strawberry.ncifcrf.gov (strawberry.NCIFCRF.GOV [129.43.6.74])
by mail.ncifcrf.gov (8.11.3/8.11.3) with ESMTP id h1I5qs819841
for <gpc@gnu.de>; Tue, 18 Feb 2003 00:52:54 -0500 (EST)
Received: (from toms@localhost)
by strawberry.ncifcrf.gov (8.9.3+Sun/8.9.3) id AAA13107
for gpc@gnu.de; Tue, 18 Feb 2003 00:52:54 -0500 (EST)
From: Tom Schneider <toms@ncifcrf.gov>
Message-Id: <200302180552.AAA13107@strawberry.ncifcrf.gov>
Subject: Re: gpc-20030209 (capitalization error)
In-Reply-To: <E18kzEw-0004Wr-00@adele.gerwinski.de> from "gpc-owner@gnu.de" at "Feb 18, 2003 05:20:18 am"
To: gpc@gnu.de (gpc)
Date: Tue, 18 Feb 2003 00:52:54 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL34 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200302/159
X-Sequence-Number: 1778
Frank:
> > Capitalization of definition <original> does not match <current>.
>
> "Definition" is generally not correct, since it can also be an
> applied occurrence of an identifier.
Thanks, I suspected that wasn't the right term!
> I'd prefer to have it in two lines, so the file names/line numbers
> can refer to both points of usage. But breaking a sentence in such a
> way, with a (generally) different line number in between, might be
> confusing. So I'd then suggest something like:
>
> foo.pas:42: capitalization of identifier <current> does not match previous one
> foo.pas:17: previous capitalization <original>
>
> or
>
> foo.pas:42: msimatched capitalization of identifier <current>
> foo.pas:17: previous capitalization <original>
1.
mismatched :-)
2. I find this use of the term 'mismatched' to be confusing. Line 42
does not stand by itself. Mismatched to what? Oh, that. It doesn't
flow in logical order.
3. It's a bit confusing if you read it rapidly in one go and think
it is one sentence.
So I think the other example is better:
> foo.pas:42: capitalization of identifier <current> does not match previous one
> foo.pas:17: previous capitalization <original>
A tiny bit of punctuation would help:
foo.pas:42: Capitalization of identifier "<current>" doesn't match original one.
foo.pas:17: The original capitalization is "<original>".
Note that I substituted 'original' throughout for clarity. (Surely
you don't mean the *previous* one - the one that just preceeded? In
that case it would yell for the third item in this series: Knifefish
... KnifeFish ... Knifefish. I would think it should only object to
the second one.)
Ok, now to tighten the screws and make is it shorter:
foo.pas:42: Identifier "<current>" capitalization doesn't match original.
foo.pas:17: The original capitalization is "<original>".
so:
foo.pas:42: Identifier "KnifeFish" capitalization doesn't match original.
foo.pas:17: The original capitalization is "Knifefish".
:-)
Tom
Dr. Thomas D. Schneider
National Cancer Institute
Laboratory of Experimental and Computational Biology
Frederick, Maryland 21702-1201
toms@ncifcrf.gov
permanent email: toms@alum.mit.edu (use only if first address fails)
http://www.lecb.ncifcrf.gov/~toms/
Previous mail
Next mail
Formatted
Overview 10 days
Subject
Date
Thread
Author
| Author | Subject | Date |
|---|---|---|
| Frank Heckenbach | gpc-20030209 (capitalization error) | 18 Feb 2003, 19:19:26 |
Note: This page contains information that does not originate from the owner of this web site, but from the authors of the mails archived. The owner of this web site is not responsible for the content of such information. Any use of that infomation requires the consent of the respective author.
Where WWW addresses (URLs) in the mails archived are marked as hyperlinks, this is only for the comfort of the reader. The content of the web pages linked to like this does not necessarily reflect the opinion of the owner of this web site or of the authors of the mails archived. The owner of this web site is not responsible for the content of such web pages. Those pages are explicitly not to be considered as part of the content of this page, but merely as references.
This page was created by Crystal 0.999 (Linux 2.4.27/i686).