Bug 285098 - s/uninitialilsed/uninitialized/ everywhere in the memcheck sources
Summary: s/uninitialilsed/uninitialized/ everywhere in the memcheck sources
Status: RESOLVED INTENTIONAL
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.7 SVN
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-27 14:55 UTC by Timur Iskhodzhanov
Modified: 2011-11-05 18:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timur Iskhodzhanov 2011-10-27 14:55:36 UTC
http://www.google.com/search?q=uninitialized -> 2.4KK results
http://www.google.com/search?q=uninitialised -> 180K results, most of them citing Valgrind

2.4KK > 10 * 180K

AFAIU, "uninitialised" is British English, whilst "...zed" is American?

---
$ grep -r uninitialised memcheck/ | grep -v "\.svn" | wc -l
868
$ grep -r uninitialized memcheck/ | grep -v "\.svn" | wc -l
19  ->  most of them are -Wno-uninitialized
Comment 1 Florian Krohm 2011-10-27 15:19:07 UTC
(In reply to comment #0)
> http://www.google.com/search?q=uninitialized -> 2.4KK results
> http://www.google.com/search?q=uninitialised -> 180K results, most of them
> citing Valgrind
> 
> 2.4KK > 10 * 180K
> 

Bollocks. What kind of argument is this?
Comment 2 Julian Seward 2011-10-28 02:10:26 UTC
Yeah.  Also, British English works OK for me :-)
Comment 3 Timur Iskhodzhanov 2011-10-28 09:23:59 UTC
gcc uses "initialized".
I don't insist much, just prefer when tools from the same ecosystem use the same language. Feel free to ignore if this isn't enough to convince.

// Background on "why?" - see bug 256525, had to support both
// Memcheck:Uninitialized and Memcheck:Uninitialised after
// getting the latter due to vim autocompletion :)