How do you think about the flooding of bracket?

[Boris Wang]

The problem is not about {} and BEGIN/END.

Because in D, we can define the function when declare, so the syntax, such 
private: static: public{}, should be discarded.

"Hasan Aljudy" <hasan.aljudy at gmail.com> 
??????:e6rhq4$1ce3$1 at digitaldaemon.com...
>I think technically these { things } are called curly braces.
> I love them. 100x times better than begin end. IMO, they make 
> function/class bodies standout.
>
> As for the second question, well, for the example you've given, I'd blame 
> the coder who wrote it.
>
> Boris Wang wrote:
>> First, now, in a function of D, we can make netsted structure, nested 
>> function and versioned code block, so much brackets, which are not code 
>> block ,in the code sequence.
>>
>> Second, the use of colon and bracket for private/public, static and 
>> version keyword, make the judge of access level and storage type is 
>> difficult.
>>
>>   class aClass
>>   {
>>     public:
>>       .
>>       .
>>       ...three pages
>>       .
>>       void func( ...)
>>       {
>>
>>        }
>>      .
>>      .
>>      static:
>>       .
>>       ... four pages
>>       .
>>       int gotit(){...}
>>
>> How do you think about all these ?
>>
>>
>