[cfe-commits] [libcxx] r119611 - /libcxx/trunk/include/algorithm

[Chris Lattner]

Yep, exactly!

-Chris

On Nov 20, 2010, at 4:21 PM, John McCall <rjmccall at apple.com> wrote:

> 
> On Nov 20, 2010, at 4:16 PM, Chris Lattner wrote:
> 
>> 
>> On Nov 20, 2010, at 3:57 PM, John McCall wrote:
>> 
>>>> 
>>>> I agree that it would make it easier to read/know.  On the other hand, /* */ comments have a nice vectorized comment skipper and // don't (and can't reasonably).  It probably isn't measurable, but this means that // comments are slower to lex than /* comments :-)
>>> 
>>> If you're really concerned about this, you *can* put BCPL comments inside C comments.  I, too, frequently find myself confused when looking at these headers because of the lengthy comments-than-don't-look-like-comments.
>> 
>> Yeah, but that also defeats the vectorized comment skipper:
> 
> Ah, right.  Then the other standard convention is to prefix such lines with '*', i.e.
>  /*
>   *  void *malloc(size_t);
>   *  void free(void*);
>   */
> In fact, that convention is so common that I assume it's why the vectorized comment skipper looks for '/' instead of '*'.
> 
> John.