"Matthew Wilson" <dmd@synesis.com.au> wrote in message news:aeko4c$20jb$1@digitaldaemon.com...
> Nope, disagree.
>
> Part of the ethos of D seems to be to answer many of the questions that other languages/compilers have left to be "implementation dependent". C & C++, for example, do not even have warnings mentioned in their standards, beyond saying that a compiler may provide warnings! D aims to answer many
of
> these previously imponderables and tie up the loose ends.
>
> Coding standards are constraints placed on code by development organisations, and are a necessary and important part of working
effectively
> in teams (or on one's own, for that matter). They are just as important on
a
> practical basis as the constraints imposed by a language, such as
rejecting
> uninitialised variables.
>
> The thing with coding standards is that they differ being subject to fashions and whims in their detail. This does not mean they are not as important, just that their nature is variable. Thus it is entirely in keeping with D to facilitate tight control of code's conformance to coding standards, whilst being mindful of the varied nature of such.
>
> Walter, I'd be interested in hearing your opinion on the idea

I think style is a matter of personal taste. Although I think everyone should use my personal favorite style <g>, about 20 years ago I gave up on the style wars as being a problem with no solution. With D, I have opted for a "D Style Guide" as a recommendation for people looking for a style to adopt, but not as a requirement for using the language.

Walter wrote:

> 
> "Matthew Wilson" <dmd@synesis.com.au> wrote in message news:aeko4c$20jb$1@digitaldaemon.com...
>> Nope, disagree.
>>
>> Part of the ethos of D seems to be to answer many of the questions that other languages/compilers have left to be "implementation dependent". C & C++, for example, do not even have warnings mentioned in their standards, beyond saying that a compiler may provide warnings! D aims to answer many
> of
>> these previously imponderables and tie up the loose ends.
>>
>> Coding standards are constraints placed on code by development organisations, and are a necessary and important part of working
> effectively
>> in teams (or on one's own, for that matter). They are just as important
>> on
> a
>> practical basis as the constraints imposed by a language, such as
> rejecting
>> uninitialised variables.
>>
>> The thing with coding standards is that they differ being subject to fashions and whims in their detail. This does not mean they are not as important, just that their nature is variable. Thus it is entirely in keeping with D to facilitate tight control of code's conformance to coding standards, whilst being mindful of the varied nature of such.
>>
>> Walter, I'd be interested in hearing your opinion on the idea
> 
> I think style is a matter of personal taste. Although I think everyone should use my personal favorite style <g>, about 20 years ago I gave up on the style wars as being a problem with no solution. With D, I have opted for a "D Style Guide" as a recommendation for people looking for a style to adopt, but not as a requirement for using the language.


Hello,
There is a D style guide.. Were can I find this, I am sure it would be
helpfull.. Come to think of it, I am sure that following your style guide
would help with optimization in code gen :)...

Ben

"ben" <zander@echotech.ca> wrote in message news:afupkr$1is8$2@digitaldaemon.com...

> Hello,
> There is a D style guide.. Were can I find this, I am sure it would be
> helpfull.. Come to think of it, I am sure that following your style guide
> would help with optimization in code gen :)...
>
> Ben

http://www.digitalmars.com/d/dstyle.html

or

on the D website under "Style Guide".