On 7/15/2011 12:46 PM, Walter Bright wrote:
> On 7/15/2011 7:25 AM, Trass3r wrote:
>> And there's lots of D code using that awkward
>> if () {
>> }
>>
>> style. Gross!
> 
> I don't particularly like that style, either, but it's used in the ebook because display size is extremely limited and it's more compact.

I find this a strong, objective argument in its favor. Stylistics preferences are one thing, but when you're stuck coding on a 15-inch widescreen laptop, those extra newlines become a real pain, because you see less code at the same time, which results in lots of scrolling.

On 7/15/11, Walter Bright <newshound2@digitalmars.com> wrote:
> On 7/15/2011 7:25 AM, Trass3r wrote:
>> And there's lots of D code using that awkward
>> if () {
>> }
>>
>> style. Gross!
>
> I don't particularly like that style, either, but it's used in the ebook
> because
> display size is extremely limited and it's more compact.
>

Hey Walter, you have a really kinky coding style!!:

if()
{ yayStatement();
}

LOL. :P

On 7/17/2011 2:09 PM, Andrej Mitrovic wrote:
> Hey Walter, you have a really kinky coding style!!:
>
> if()
> { yayStatement();
> }

That was born of the days of programming using 24 line tty's.

Roman Ivanov wrote:
> On 7/15/2011 12:46 PM, Walter Bright wrote:
>> On 7/15/2011 7:25 AM, Trass3r wrote:
>>> And there's lots of D code using that awkward
>>> if () {
>>> }
>>>
>>> style. Gross!
>> I don't particularly like that style, either, but it's used in the ebook because display size is extremely limited and it's more compact.
> 
> I find this a strong, objective argument in its favor. Stylistics preferences are one thing, but when you're stuck coding on a 15-inch widescreen laptop, those extra newlines become a real pain, because you see less code at the same time, which results in lots of scrolling.

	This is the main reason why I prefer this style...

		Jerome
-- 
mailto:jeberger@free.fr
http://jeberger.free.fr
Jabber: jeberger@jabber.fr