Displaying 2 results from an estimated 2 matches for "vk_argument".
Did you mean:
no_argument
2010 Nov 30
0
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
...e same rules as types. If there is a doubt, the enum should be a "Kind", e.g. "ValueTy" in llvm/Value.h should be "ValueKind".
Enumerators (unless they are in their own small namespace) should have a prefix. For example, the enumerators in the ValueTy enum should be VK_Argument, VK_BasicBlock, etc. These rules shouldn't apply to enums that are just convenience constants, like:
enum {
MaxSize = 42,
Density = 12
};
These should follow the same rules as ivars if they are members of classes.
Thank you for driving this forward Zhanyong, I think that this will make...
2010 Nov 29
3
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
On Sun, Nov 28, 2010 at 11:02 PM, 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