This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 1/*] Fix common typos.
- From: Mike Stump <mikestump at comcast dot net>
- To: OndÅej BÃlka <neleai at seznam dot cz>
- Cc: "gcc-patches at gcc dot gnu dot org Patches" <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 21 Jul 2013 11:53:39 -0700
- Subject: Re: [PATCH 1/*] Fix common typos.
- References: <20130721143204 dot GA27788 at domone> <48EB8081-EBEE-4551-A34E-EBC4339DE522 at comcast dot net>
On Jul 21, 2013, at 11:31 AM, Mike Stump <mikestump@comcast.net> wrote:
> On Jul 21, 2013, at 7:32 AM, OndÅej BÃlka <neleai@seznam.cz> wrote:
>> This is series of typo fixing patches.
>
> I reviewed gcc/[a-i]* and checked in those I thought were trivial.
So, I checked in the potentially controversial thru -> through in gcc/ada. I'll let the ada folks contemplate this and decide if they do in fact prefer thru in gcc/ada. I'll just note that in a googlefight of gcc/*.[ch] and gcc/doc/*.texi, through does win out except for words like fall-thru and abbreviations in function names, in which it is entirely appropriate. thru occurs 0 times, through occurs 1584 times.
Since I was doing google fights in the code:
up:gcc mrs$ grep '\<OK\>' *.[ch] doc/*.texi | grep -v _OK | wc -l
95
up:gcc mrs$ grep '\<ok\>' *.[ch] doc/*.texi | grep -v _ok | wc -l
286
:-) I thought I would share.