On Tue, Nov 17, 2009 at 10:39 PM, Darin Adler wrote:
> On Nov 16, 2009, at 7:54 PM, Chris Jerdonek wrote:
>
>> So, I was wondering if we can clarify the rule to apply only to the
>> outermost namespace declaration.
>
> Yes, I think we can.
>
>> (Consecutive declarations like "namespace JSC { nam
On Nov 18, 2009, at 10:03 AM, Alexey Proskuryakov wrote:
> I actually prefer no comment after the namespace ending brace. If I have any
> concerns about namespaces not being properly closed, I won't believe the
> comment anyway, and will check by double-clicking on the closing brace to
> select
16.11.2009, в 19:54, Chris Jerdonek написал(а):
Second, do people prefer nested namespace blocks to end with the
fully-qualified name (e.g. // namespace JSC::WREC) or just the final
name (e.g. // namespace WREC)? I have seen both.
I actually prefer no comment after the namespace ending brac
On Nov 16, 2009, at 7:54 PM, Chris Jerdonek wrote:
> First, it seems like the original motive was to avoid pointlessly indenting
> nearly the whole file:
>
> https://lists.webkit.org/pipermail/webkit-dev/2009-September/010002.html
>
> So, I was wondering if we can clarify the rule to apply only
I am contemplating a script to normalize the namespace indenting
across our code to match our guidelines, so I wanted to clarify two
things. First, it seems like the original motive was to avoid
pointlessly indenting nearly the whole file:
https://lists.webkit.org/pipermail/webkit-dev/2009-Septem
5 matches
Mail list logo
