<div dir="ltr">Oh jeez, typical ... Accidentally sent this only to Krzysztof instead of everyone; my apologies for duplicate.<div><br></div><div>----</div><div><br></div><div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">
If I may pitch in, yes, very true, but I would personally categorize this as a nomenclature problem, in which case is quite important to have same naming convention for things. Examples of literature that strive to be similarly unambiguous are things like references and user manuals; if chapter 1 is in English and chapter 2 is in German, it wouldn't be very nice. Additionally, same word in two languages frequently means a vastly different thing :)</div>
<div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px"><br></div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">In that light, I'd say things like naming conventions (M for module, V1...V2 for vars, etc) and whether to use CamelCase or not are really quite important. Some automatic assumptions that you end up acquiring, such as wether something is a variable, class or something else break completely otherwise (*especially* if you work on two projects at once). Another thing I rate quite highly is tabs/spaces/number of spaces convention. While you can configure your editor to have different settings based on file type, it becomes a nuisance when dealing with only one type (ie. C++). The problem is especially aggravated in case if, for, etc. blocks don't necessarily have {} around them (and I've seen that in LLVM/Clang at least a few times). On the other hand, things like whether lines occasionally go over 80 character limits (and I dont mean like 120 chars) or if initializer lists have leading commas, well, among other issues that's likely not lethal. As opposed to capitalizing variables or not, there is no ambiguity incurred.</div>
<div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px"><br></div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">Finally, I'd imagine status quo coding standard will eventually grow on folks who have hard time switching instantly. In the process, some aspects might also migrate the other way into LLVM core, which may very well be a good thing.</div>
<div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px"><br></div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">Cheers,</div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">
<br></div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px"><br></div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">Dimitri.</div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Jan 22, 2013 at 2:35 PM, Krzysztof Parzyszek <span dir="ltr"><<a href="mailto:kparzysz@codeaurora.org" target="_blank">kparzysz@codeaurora.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 1/22/2013 4:15 PM, Chandler Carruth wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
A different naming convention is one of the most disruptive things to<br>
have change between two code bases. It will cause people to habitually<br>
write code one way, realize they are submitting to the other repository,<br>
and have to mechanically go and rename all their variables. While I<br>
personally like your naming convention slightly better than LLVM's, and<br>
a few other conventions slightly better than yours, I really don't care.<br>
</blockquote>
<br></div>
FWIW, I think this is like switching between spoken languages. At the beginning you can get things mixed up, but once you gain proficiency, you can use either without difficulty.<span class="HOEnZb"><font color="#888888"><br>
<br>
-Krzysztof<br>
<br>
-- <br>
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/llvmdev</a><br>
</div></div></blockquote></div><br></div>