Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
VIA releases open source Xorg driver
Posted Aug 29, 2008 22:35 UTC (Fri) by JoeBuck (subscriber, #2330)
Over the years I've seen a lot of code where the comments, variable names, etc. are chosen from some other language.
Posted Aug 30, 2008 11:38 UTC (Sat) by tzafrir (subscriber, #11501)
Posted Aug 30, 2008 15:02 UTC (Sat) by rahulsundaram (subscriber, #21946)
Posted Aug 30, 2008 19:19 UTC (Sat) by salimma (subscriber, #34460)
Posted Aug 31, 2008 2:47 UTC (Sun) by rahulsundaram (subscriber, #21946)
Posted Sep 1, 2008 8:05 UTC (Mon) by dgm (subscriber, #49227)
Regarding English, the distance from being able to read to being able to express yourself is considerable. I haven't been to Taiwan, but in mainland China the percentage of people that can read English is very small.
Posted Aug 31, 2008 20:25 UTC (Sun) by xtifr (subscriber, #143)
And, of course, without a knowledge of English, the fact that "stdio" might be short for "standard input/output" will be completely lost on you. (Even with English, this might not be obvious at first.)
Ironically, because the default locale is 8-bit ascii, you'll need to know <em>more</em> English words to write a program that works in another language than you would to write one that works in English. At a minimum, you'll need to learn "locale" and "set". Neither of which, again, are keywords or even parts of keywords. :)
This isn't to say that you <em>can't</em> learn to program in C with only a bare minimum knowledge of English--we've both seen it done. But the bar is still higher than you suggest--"a few keywords" is far from sufficient.
Posted Sep 1, 2008 14:45 UTC (Mon) by proski (subscriber, #104)
Posted Sep 4, 2008 5:55 UTC (Thu) by ncm (subscriber, #165)
Posted Sep 4, 2008 8:39 UTC (Thu) by ekj (guest, #1524)
You may need to understand what printf, strstr, mutex, heap, CreateNode, while, string, for and a lot of stuff like that means.
But the fact that these are origined in english is almost completely unimportant, a non-programming english-native would not be able to tell what a "heap" or a "mutex" is in this context any better than a non-programming Indian or Norwegian or whatever.
When he -does- learn programming, he also learns the spesific meaning of the most common words, he learns more when he uses libraries etc. But here's the thing; this spesific meaning is so specialised that knowledge of what the word means in everyday english is almost completely irrelevant.
It's -not- much easier to learn what a "heap" is in programming-context if you're a native english-speaker than it is if you know no english at all.
Try asking your grandmother (assuming she is english native, and does no programming) what a "string" or a "heap" is. You'll get an answer, but not one that would help much in understanding a C-program.
Posted Sep 4, 2008 9:29 UTC (Thu) by nix (subscriber, #2304)
Posted Sep 5, 2008 12:14 UTC (Fri) by ekj (guest, #1524)
German, Norwegian, French, Italian and Spanish all have a few extra letters and/or apostrophes or whatever. Nevertheless it's simple to use norwegian (or german, or italian) names for variables, functions and components.
Even if you -do- decide to use english names, that's STILL not equivalent to needing to know the language. You don't need hearing-comprehension (harder than reading-comprehension for many) you don't need grammar. You don't need pronounciation. You don't need comma-rules, capitalization-rules etc etc etc.
Learning a few nouns and a few verbs isn't more than a small part of learning a language.
Knowing english is helpful. It's in no way required.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds