GNU Pascal Homepage - gpc - gpc-announce - gpc-de - gpc-doc
This page in English

Mail #8036 (Unformatiert/Volle Header)

Zurück zur Archiv-Hauptseite

Vorige Mail   Nächste Mail   Formatiert
Übersicht  10 Tage   Betreff   Datum   Thread   Autor  

From gpc-owner@gnu.de  Wed Feb 19 05:38:03 2003
Received: from mail.ncifcrf.gov ([129.43.100.100])
	by adele.gerwinski.de with esmtp (Exim 3.35 #1 (Debian))
	id 18lLzZ-00072Z-00
	for <gpc@gnu.de>; Wed, 19 Feb 2003 05:37:57 +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 h1J4bt800443
	for <gpc@gnu.de>; Tue, 18 Feb 2003 23:37:55 -0500 (EST)
Received: (from toms@localhost)
	by strawberry.ncifcrf.gov (8.9.3+Sun/8.9.3) id XAA16567
	for gpc@gnu.de; Tue, 18 Feb 2003 23:37:54 -0500 (EST)
From: Tom Schneider <toms@ncifcrf.gov>
Message-Id: <200302190437.XAA16567@strawberry.ncifcrf.gov>
Subject: Re: gpc-20030209 (capitalization error)
In-Reply-To: <E18lLib-0004oc-00@adele.gerwinski.de> from "gpc-owner@gnu.de" at "Feb 19, 2003 05:20:25 am"
To: gpc@gnu.de (gpc)
Date: Tue, 18 Feb 2003 23:37: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/177
X-Sequence-Number: 1796

> > 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/

Vorige Mail   Nächste Mail   Formatiert
Übersicht  10 Tage   Betreff   Datum   Thread   Autor  


Antworten auf diese Mail

Autor Betreff Datum
Frank Heckenbach gpc-20030209 (capitalization error) 19.2.2003, 10:15:32

Zurück zur Archiv-Hauptseite


Hinweis: Diese Seite enthält Informationen, die nicht vom Betreiber dieser Website, sondern von den Autoren der archivierten Mails stammen. Der Betreiber dieser Website ist nicht für den Inhalt dieser Informationen verantwortlich. Die weitere Verwendung dieser Informationen bedarf des Einverständnisses des jeweiligen Autors.

Sofern WWW-Adressen (URLs) in den archivierten Mails als Hyperlinks hervorgehoben werden, so geschieht dies ausschließlich zur Annehmlichkeit für den Leser. Der Inhalt der auf diese Weise angelinkten Webseiten spiegelt nicht notwendigerweise die Meinung des Betreibers dieser Webseite oder der Autoren der archivierten Mails wider. Der Betreiber dieser Webseite ist nicht für den Inhalt solcher Webseiten verantwortlich. Diese Seiten sind ausdrücklich nicht als Teil des Inhalts dieser Seite zu betrachten, sondern lediglich als Referenzen.


Diese Seite wurde erzeugt von Crystal 0.999 (Linux 2.4.27/i686).