Displaying 3 results from an estimated 3 matches for "unix_hacker".
2010 Dec 04
0
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
On Dec 3, 2010, at 8:03 PM, Thiago Farina wrote:
> On Mon, Nov 29, 2010 at 5:02 AM, Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
>>> I enjoyed the new coding style in recent patches. Camel case makes it easy
>>> to pick a descriptive name. Starting functions and variables with lower
>>> cases reduces chances to conflict with a type name.
>>
2010 Dec 05
2
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
...ng CamelCase (MyClass, for
example) and the instance of MyClass is my_class. That avoids many
confusions in my brain.
This convention used here: MyClass* MC = new MyClass, is an obstacle
for external contributors used to work with C for example, where
almost everything (and every project) uses the unix_hacker style.
2010 Dec 04
2
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
On Mon, Nov 29, 2010 at 5:02 AM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>> I enjoyed the new coding style in recent patches. Camel case makes it easy
>> to pick a descriptive name. Starting functions and variables with lower
>> cases reduces chances to conflict with a type name.
> Honestly speaking, I don't. Especially in the cases when varname is