Previous mail
Next mail
Unformatted/full headers
Overview 10 days
Subject
Date
Thread
Author
From: Tom Schneider
Subject: gpc-20030209 (capitalization error)
Date: 18 Feb 2003, 23:37:54
> > 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>".
>
> Well, most other errors don't include puncutation, and no complete
> sentences. So it would be unsystematic to make this one different.
Sigh. Maybe it's time to start making them more clear? If not, how
about:
foo.pas:42: capitalization of identifier "<current>" doesn't match original one
foo.pas:17: the original capitalization is "<original>"
The quote marks would help.
> > 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.)
>
> No, sorry. Storing *all* capitalisations is extra effort. Since
> someone who uses this warning is supposed to want uniform
> capitalisation, I don't think the effort is worth it ...
No, I thought that you would only store the first one ("original") and
compare all later ones ("current") to that. Generally the first one
is the definition, so this should work fine. In this case it WOULD
only object to the second case. If, on the other hand, you store the
PREVIOUS one, it would object to both the second KnifeFish AND the
third Knifefish, even though that matches the original (first)
definition. That could be rather confusing to someone. ("Why is it
yelling at me for this one? It's right!")
Hmm. I just realized that there is a question of scope here. Are you
making a pushdown stack for this?
var Knifefish ...
procedure capture;
var KnifeFish ...
begin
...
end;
It should not object to this case.
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
Unformatted/full headers
Overview 10 days
Subject
Date
Thread
Author
| Author | Subject | Date |
|---|---|---|
| Frank Heckenbach | gpc-20030209 (capitalization error) | 19 Feb 2003, 10:15:32 |
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).