On 11/10/2014 02:00 PM, H. S. Teoh via Digitalmars-d-learn wrote:
> (I kid you not, people
> actually exist who write code like this):
I know one of those people! They are from a different era. :)
>int my_func(int arg) {
>if (arg==1) {
>printf("One\n");
>
On Mon, 10 Nov 2014 14:00:32 -0800
"H. S. Teoh via Digitalmars-d-learn"
wrote:
> I used to be an Egyptian-braces / tabs-only-indentation advocate. That
> works reasonably well in C/C++, but I find that with idiomatic D, Phobos
> style actually works much better. (Well, except that horrid camelCas
On Monday, 10 November 2014 at 22:04:20 UTC, H. S. Teoh via
Digitalmars-d-learn wrote:
No idea what you're talking about, but I was referring to
squishingAllWordsIntoOneUnreadableMess vs.
keeping_them_visually_separate_and_readable.
I like the keeping_the_visually_separate_and_readable when it
On Mon, Nov 10, 2014 at 09:36:18PM +, via Digitalmars-d-learn wrote:
> On Monday, 10 November 2014 at 19:37:06 UTC, H. S. Teoh via
> Digitalmars-d-learn wrote:
> >I have to say that I *hate* camelCase... it looks really ugly. But
> >what looks uglier is a mixture of camelCase and something else
On Mon, Nov 10, 2014 at 11:27:13PM +0200, ketmar via Digitalmars-d-learn wrote:
> On Mon, 10 Nov 2014 11:35:04 -0800
> "H. S. Teoh via Digitalmars-d-learn"
> wrote:
>
> > I have to say that I *hate* camelCase... it looks really ugly. But
> > what looks uglier is a mixture of camelCase and somethi
On Monday, 10 November 2014 at 19:37:06 UTC, H. S. Teoh via
Digitalmars-d-learn wrote:
I have to say that I *hate* camelCase... it looks really ugly.
But what
looks uglier is a mixture of camelCase and something else.
Ah, but here I disagree. I like to use different formatting for
different l
On Mon, 10 Nov 2014 11:35:04 -0800
"H. S. Teoh via Digitalmars-d-learn"
wrote:
> I have to say that I *hate* camelCase... it looks really ugly. But what
> looks uglier is a mixture of camelCase and something else. And since
> Phobos is all camelCased, and almost all D code uses Phobos, writing
>
Hard styling rules only apply to Phobos contributions. Any other
project can have their own, for example, vibe.d requires own
style which is incompatible with Phobos.
For ported 3d party library value of minimizing the diff is
indeed more important than styling.
On Mon, Nov 10, 2014 at 09:19:58PM +0200, ketmar via Digitalmars-d-learn wrote:
> On Mon, 10 Nov 2014 16:16:04 +
> "Adam D. Ruppe via Digitalmars-d-learn"
> wrote:
>
> > Personally, I don't really care about naming conventions. I prefer
> > the camelCase and it seems most D people do, but if
On Mon, 10 Nov 2014 16:16:04 +
"Adam D. Ruppe via Digitalmars-d-learn"
wrote:
> Personally, I don't really care about naming conventions. I
> prefer the camelCase and it seems most D people do, but if you're
> translating another library, there's value it keeping it the same
> for ease of
On 2014-11-10 11:16 AM, Adam D. Ruppe wrote:
Personally, I don't really care about naming conventions. I prefer the
camelCase and it seems most D people do, but if you're translating
another library, there's value it keeping it the same for ease of
documentation lookups from the original etc.
I
Personally, I don't really care about naming conventions. I
prefer the camelCase and it seems most D people do, but if you're
translating another library, there's value it keeping it the same
for ease of documentation lookups from the original etc.
Etienne:
I'm translating the library Botan and I'm at a point where I
have to ask myself if I'm going to change functions and object
names respectively from snake_case and Camel_Case to camelCase
and CamelCase. Same goes for file names. Is this a strict rule
for D libraries?
Take a look:
ht
I'm translating the library Botan and I'm at a point where I have to ask
myself if I'm going to change functions and object names respectively
from snake_case and Camel_Case to camelCase and CamelCase. Same goes for
file names. Is this a strict rule for D libraries?
14 matches
Mail list logo
