Have a look here: 5724a487e9ac940d4136584ecd3b496563b81263
I don't think this is a good idea since the NK prefix doesn't tell the programmer that the expected values are CFRange values, like a NSMaxRange tells him that it expects a NSRange struct.
I'd propose sticking with just e.g. CFMaxRange without the prefix. NKCF is kind of long.
Have a look here: 5724a487e9ac940d4136584ecd3b496563b81263
I don't think this is a good idea since the
NK
prefix doesn't tell the programmer that the expected values areCFRange
values, like aNSMaxRange
tells him that it expects aNSRange
struct.I'd propose sticking with just e.g.
CFMaxRange
without the prefix.NKCF
is kind of long.