Re: [lldb-dev] LLDB Evolution

2016-08-28 Thread Chris Lattner via lldb-dev 
Can you just grep for “^“ or something?  That 
seems like a straight-forward way to find lines that have a ton of leading 
indentation.

-Chris

> On Aug 27, 2016, at 9:28 AM, Zachary Turner  wrote:
> 
> It will probably be hard to find all the cases.  Unfortunately clang-tidy 
> doesn't have a "detect deep indentation" check, but that would be pretty 
> useful, so maybe I'll try to add that at some point (although I doubt I can 
> get to it before the big reformat).
> 
> Finding all of the egregious cases before the big reformat will present a 
> challenge, so I'm not sure if it's better to spend effort trying, or just 
> deal with it as we spot code that looks bad because of indentation level.
> 
> On Sat, Aug 27, 2016 at 9:24 AM Chris Lattner  > wrote:
>> On Aug 26, 2016, at 6:12 PM, Zachary Turner via lldb-dev 
>> mailto:lldb-dev@lists.llvm.org>> wrote:
>> 
>> Back to the formatting issue, there's a lot of code that's going to look bad 
>> after the reformat, because we have some DEEPLY indented code.  LLVM has 
>> adopted the early return model for this reason.  A huge amount of our deeply 
>> nested code could be solved by using early returns. 
> 
> FWIW, early returns are part of the LLVM Coding standard:
> http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code
>  
> 
> 
> So it makes sense for LLDB to adopt this approach at some point.
> 
> I don’t have an opinion about whether it happens before or after the "big 
> reformat", but I guess I agree with your point that doing it would be good to 
> do it for the most egregious cases before the reformat.
> 
> -Chris

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Evolution

2016-08-28 Thread Zachary Turner via lldb-dev 
I tried that, but most of the results (and there are a ton to wade through)
are function parameters that wrapped and align with the opening paren on
the next line.

Earlier in the thread (i think it was this thread anyway) i posted a bash
incantation that will grep the source tree and return all lines with >= N
leading spaces sorted descending by number of leading spaces. The highest
was about 160 :)

If you search lldb-dev for awk or sed you'll probably find it
On Sun, Aug 28, 2016 at 9:10 AM Chris Lattner  wrote:

> Can you just grep for “^“ or something?
> That seems like a straight-forward way to find lines that have a ton of
> leading indentation.
>
> -Chris
>
> On Aug 27, 2016, at 9:28 AM, Zachary Turner  wrote:
>
> It will probably be hard to find all the cases.  Unfortunately clang-tidy
> doesn't have a "detect deep indentation" check, but that would be pretty
> useful, so maybe I'll try to add that at some point (although I doubt I can
> get to it before the big reformat).
>
> Finding all of the egregious cases before the big reformat will present a
> challenge, so I'm not sure if it's better to spend effort trying, or just
> deal with it as we spot code that looks bad because of indentation level.
>
> On Sat, Aug 27, 2016 at 9:24 AM Chris Lattner  wrote:
>
>> On Aug 26, 2016, at 6:12 PM, Zachary Turner via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>> Back to the formatting issue, there's a lot of code that's going to look
>> bad after the reformat, because we have some DEEPLY indented code.  LLVM
>> has adopted the early return model for this reason.  A huge amount of our
>> deeply nested code could be solved by using early returns.
>>
>>
>> FWIW, early returns are part of the LLVM Coding standard:
>>
>> http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code
>>
>> So it makes sense for LLDB to adopt this approach at some point.
>>
>> I don’t have an opinion about whether it happens before or after the "big
>> reformat", but I guess I agree with your point that doing it would be good
>> to do it for the most egregious cases before the reformat.
>>
>> -Chris
>>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Evolution

2016-08-28 Thread Zachary Turner via lldb-dev 
Here it is


grep -n '^ \+' . -r -o | awk '{t=length($0);sub(" *$","");printf("%s%d\n",
$0, t-length($0));}' | sort -t: -n -k 3 -r | awk 'BEGIN { FS = ":" } ; { if
($3 >= 50) print $0 }'
On Sun, Aug 28, 2016 at 9:54 AM Zachary Turner  wrote:

> I tried that, but most of the results (and there are a ton to wade
> through) are function parameters that wrapped and align with the opening
> paren on the next line.
>
> Earlier in the thread (i think it was this thread anyway) i posted a bash
> incantation that will grep the source tree and return all lines with >= N
> leading spaces sorted descending by number of leading spaces. The highest
> was about 160 :)
>
> If you search lldb-dev for awk or sed you'll probably find it
> On Sun, Aug 28, 2016 at 9:10 AM Chris Lattner  wrote:
>
>> Can you just grep for “^“ or something?
>> That seems like a straight-forward way to find lines that have a ton of
>> leading indentation.
>>
>> -Chris
>>
>> On Aug 27, 2016, at 9:28 AM, Zachary Turner  wrote:
>>
>> It will probably be hard to find all the cases.  Unfortunately clang-tidy
>> doesn't have a "detect deep indentation" check, but that would be pretty
>> useful, so maybe I'll try to add that at some point (although I doubt I can
>> get to it before the big reformat).
>>
>> Finding all of the egregious cases before the big reformat will present a
>> challenge, so I'm not sure if it's better to spend effort trying, or just
>> deal with it as we spot code that looks bad because of indentation level.
>>
>> On Sat, Aug 27, 2016 at 9:24 AM Chris Lattner  wrote:
>>
>>> On Aug 26, 2016, at 6:12 PM, Zachary Turner via lldb-dev <
>>> lldb-dev@lists.llvm.org> wrote:
>>>
>>> Back to the formatting issue, there's a lot of code that's going to look
>>> bad after the reformat, because we have some DEEPLY indented code.  LLVM
>>> has adopted the early return model for this reason.  A huge amount of our
>>> deeply nested code could be solved by using early returns.
>>>
>>>
>>> FWIW, early returns are part of the LLVM Coding standard:
>>>
>>> http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code
>>>
>>> So it makes sense for LLDB to adopt this approach at some point.
>>>
>>> I don’t have an opinion about whether it happens before or after the
>>> "big reformat", but I guess I agree with your point that doing it would be
>>> good to do it for the most egregious cases before the reformat.
>>>
>>> -Chris
>>>
>>
>>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Evolution

2016-08-28 Thread Tamas Berghammer via lldb-dev 
You can grep for "  {$". With this regex I
see no false positives and 272 case with 40 or more leading spaces

On Sun, 28 Aug 2016, 17:59 Zachary Turner via lldb-dev, <
lldb-dev@lists.llvm.org> wrote:

> Here it is
>
>
> grep -n '^ \+' . -r -o | awk '{t=length($0);sub(" *$","");printf("%s%d\n",
> $0, t-length($0));}' | sort -t: -n -k 3 -r | awk 'BEGIN { FS = ":" } ; { if
> ($3 >= 50) print $0 }'
> On Sun, Aug 28, 2016 at 9:54 AM Zachary Turner  wrote:
>
>> I tried that, but most of the results (and there are a ton to wade
>> through) are function parameters that wrapped and align with the opening
>> paren on the next line.
>>
>> Earlier in the thread (i think it was this thread anyway) i posted a bash
>> incantation that will grep the source tree and return all lines with >= N
>> leading spaces sorted descending by number of leading spaces. The highest
>> was about 160 :)
>>
>> If you search lldb-dev for awk or sed you'll probably find it
>> On Sun, Aug 28, 2016 at 9:10 AM Chris Lattner  wrote:
>>
>>> Can you just grep for “^“ or something?
>>> That seems like a straight-forward way to find lines that have a ton of
>>> leading indentation.
>>>
>>> -Chris
>>>
>>> On Aug 27, 2016, at 9:28 AM, Zachary Turner  wrote:
>>>
>>> It will probably be hard to find all the cases.  Unfortunately
>>> clang-tidy doesn't have a "detect deep indentation" check, but that would
>>> be pretty useful, so maybe I'll try to add that at some point (although I
>>> doubt I can get to it before the big reformat).
>>>
>>> Finding all of the egregious cases before the big reformat will present
>>> a challenge, so I'm not sure if it's better to spend effort trying, or just
>>> deal with it as we spot code that looks bad because of indentation level.
>>>
>>> On Sat, Aug 27, 2016 at 9:24 AM Chris Lattner 
>>> wrote:
>>>
 On Aug 26, 2016, at 6:12 PM, Zachary Turner via lldb-dev <
 lldb-dev@lists.llvm.org> wrote:

 Back to the formatting issue, there's a lot of code that's going to
 look bad after the reformat, because we have some DEEPLY indented code.
 LLVM has adopted the early return model for this reason.  A huge amount of
 our deeply nested code could be solved by using early returns.


 FWIW, early returns are part of the LLVM Coding standard:

 http://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code

 So it makes sense for LLDB to adopt this approach at some point.

 I don’t have an opinion about whether it happens before or after the
 "big reformat", but I guess I agree with your point that doing it would be
 good to do it for the most egregious cases before the reformat.

 -Chris

>>>
>>> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 29178] New: how to reset skype

2016-08-28 Thread via lldb-dev 
https://llvm.org/bugs/show_bug.cgi?id=29178

Bug ID: 29178
   Summary: how to reset skype
   Product: lldb
   Version: 3.9
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: jacks...@gmail.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

account live com password reset(((1888.811.4532)))
skype change password(((1888.811.4532)))
change skype password(((1888.811.4532)))
skype recovery(((1888.811.4532)))
reset skype password(((1888.811.4532)))
skype reset password(((1888.811.4532)))
skype email address(((1888.811.4532)))
change password skype(((1888.811.4532)))
lost skype password(((1888.811.4532)))
retrieve skype password(((1888.811.4532)))
skype password recovery(((1888.811.4532)))
skype account recovery(((1888.811.4532)))
skype recover password(((1888.811.4532)))
change my skype password(((1888.811.4532)))
skype password change email(((1888.811.4532)))
reset skype(((1888.811.4532)))
reset password(((1888.811.4532)))
recover skype account(((1888.811.4532)))
skype password change(((1888.811.4532)))
recover skype password(((1888.811.4532)))

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 29188] New: skype is not working? Call 1888.811.4532

2016-08-28 Thread via lldb-dev 
https://llvm.org/bugs/show_bug.cgi?id=29188

Bug ID: 29188
   Summary: skype is not working? Call 1888.811.4532
   Product: lldb
   Version: 3.9
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: jacks...@gmail.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

video not working on skype!!~@1 888 811 4532*& no sound on skype!!~@1
888 811 4532*& skype camera not working!!~@1 888 811 4532*& webcam not
working on skype!!~@1 888 811 4532*& skype no sound!!~@1 888 811 4532*&
skype group call not working!!~@1 888 811 4532*& skype wont connect   
!!~@1 888 811 4532*& no sound in skype!!~@1 888 811 4532*& skype no audio  
 !!~@1 888 811 4532*& skype share screen not working!!~@1 888 811 4532*&
skype will not open!!~@1 888 811 4532*& skype microphone not working   
!!~@1 888 811 4532*& skype audio settings!!~@1 888 811 4532*& why wont my
skype work!!~@1 888 811 4532*& skype live chat what is a skype number,
skype customer service phone number usa, skype contacts, skype contact us,
skype number, how to contact skype, skype technical support, skype customer
service, skype phone number, skype customer service phone number, skype support
number, skype customer support, skype tech support, skype contact number, skype
customer support chat, skype customer service number, skype customer service
800 number, skype support phone number,  skype service status!!~@1 888 811
4532*& skype is down!!~@1 888 811 4532*& skype sound not working!!~@1
888 811 4532*&

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 29189] New: Call 1888.811.4532 Skype support chat

2016-08-28 Thread via lldb-dev 
https://llvm.org/bugs/show_bug.cgi?id=29189

Bug ID: 29189
   Summary: Call 1888.811.4532 Skype support chat
   Product: lldb
   Version: 3.9
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: jacks...@gmail.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

skype tech support<<1888.811.4532>> skype contact number   
<<1888.811.4532>> skype customer service phone<<1888.811.4532>> skype
password change!!~@1 888 811 4532*& skype change password!!~@1 888 811
4532*& skype password recovery!!~@1 888 811 4532*& change skype password   
!!~@1 888 811 4532*& reset skype password!!~@1 888 811 4532*& skype reset
password!!~@1 888 811 4532*& skype email address!!~@1 888 811 4532*&
recover skype password!!~@1 888 811 4532*& change password skype!!~@1
888 811 4532*& lost skype password!!~@1 888 811 4532*&  skype tech support
number<<1888.811.4532>> skype customer care<<1888.811.4532>> skype live
support<<1888.811.4532>> skype help phone number<<1888.811.4532>> skype
down today!!~@1 888 811 4532*& skype call not connecting!!~@1 888 811
4532*& mic wont work on skype!!~@1 888 811 4532*& skype not connecting
calls!!~@1 888 811 4532*& skype screen sharing not working!!~@1 888 811
4532*& microphone not working in skype!!~@1 888 811 4532*& skype network
status!!~@1 888 811 4532*& is skype working!!~@1 888 811 4532*& whats
wrong with skype!!~@1 888 811 4532*& microphone on skype not working   
!!~@1 888 811 4532*&  skype customer support chat<<1888.811.4532>> skype
customer service number<<1888.811.4532>> skype customer service 800 number 
  <<1888.811.4532>> skype support phone number<<1888.811.4532>> call skype
support<<1888.811.4532>> skype support chat<<1888.811.4532>> skype
customer service chat<<1888.811.4532>>

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev