May 28, 2013
On 5/27/2013 5:34 PM, Manu wrote:
> On 28 May 2013 09:05, Walter Bright <newshound2@digitalmars.com
> <mailto:newshound2@digitalmars.com>> wrote:
>
>     On 5/27/2013 3:18 PM, H. S. Teoh wrote:
>
>         Well, D *does* support non-English identifiers, y'know... for example:
>
>                  void main(string[] args) {
>                          int число = 1;
>                          foreach (и; 0..100)
>                                  число += и;
>                          writeln(число);
>                  }
>
>         Of course, whether that's a good practice is a different story. :)
>
>
>     I've recently come to the opinion that that's a bad idea, and D should not
>     support it.
>
>
> Why? You said previously that you'd love to support extended operators ;)

Extended operators, yes. Non-ascii identifiers, no.
May 28, 2013
On 28/05/13 09:44, H. S. Teoh wrote:

> Since language keywords are already in English, we might as well
> standardize on English identifiers too.

So you're going to spell check them all to make sure that they're English?  Or did you mean ASCII?

Peter

May 28, 2013
On Tuesday, May 28, 2013 11:38:08 Peter Williams wrote:
> On 28/05/13 09:44, H. S. Teoh wrote:
> > Since language keywords are already in English, we might as well standardize on English identifiers too.
> 
> So you're going to spell check them all to make sure that they're English?  Or did you mean ASCII?

I think that it was more an issue of that the only reason that Unicode would be necessary in identifiers would be if you weren't using English, so if you assume that everyone is going to be using some form of English for their identifier names, you can skip having Unicode in identifiers. So, a natural effect of standardizing on English is that you can stick with ASCII.

- Jonathan M Davis
May 28, 2013
On Tuesday, 28 May 2013 at 01:38:22 UTC, Peter Williams wrote:

>
> So you're going to spell check them all to make sure that they're English?  Or did you mean ASCII?
>
> Peter

That's it. I'm filing a bug against std.traits. There's a unittest there that with a struct named "Colour". Completely unacceptable.

May 28, 2013
On 28 May 2013 11:42, Jonathan M Davis <jmdavisProg@gmx.com> wrote:

> On Tuesday, May 28, 2013 11:38:08 Peter Williams wrote:
> > On 28/05/13 09:44, H. S. Teoh wrote:
> > > Since language keywords are already in English, we might as well standardize on English identifiers too.
> >
> > So you're going to spell check them all to make sure that they're English?  Or did you mean ASCII?
>
> I think that it was more an issue of that the only reason that Unicode
> would
> be necessary in identifiers would be if you weren't using English, so if
> you
> assume that everyone is going to be using some form of English for their
> identifier names, you can skip having Unicode in identifiers. So, a natural
> effect of standardizing on English is that you can stick with ASCII.
>

I'm fairly sure that any programmer who takes themself seriously will use
English, I don't see any reason why this rule should nee to be be
implemented by the compiler.
The loss I can imagine is that kids, or people from developing countries,
etc, may have an additional barrier to learning to code if they don't speak
English.
Nobody in this set is likely to produce a useful library that will be used
widely.
Likewise, no sane programmer is going to choose to use a library that's not
written in English.

You may argue that the keywords and libs are in English. I can attest from
personal experience, that a child, or a non-english-speaking beginner
probably has absolutely NO IDEA what the keywords mean anyway, even if they
do speak English.
I certainly had no idea when I was a kid, I just typed them because I
figured out what they did. I didn't even know how to say many of them, and
realised 5 years later than I was saying all the words wrong...

So my point is, why make this restriction as a static compiler rule, when
it's not practically going to be broken anyway. You never know, it may
actually assist some people somewhere.
I think it's a great thing that D can accept identifiers in non-english.


May 28, 2013
On 28 May 2013 13:22, David Eagen <davideagen@mailinator.com> wrote:

> On Tuesday, 28 May 2013 at 01:38:22 UTC, Peter Williams wrote:
>
>
>> So you're going to spell check them all to make sure that they're English?  Or did you mean ASCII?
>>
>> Peter
>>
>
> That's it. I'm filing a bug against std.traits. There's a unittest there that with a struct named "Colour". Completely unacceptable.
>

How dare you!
What's unacceptable is that a bunch of ex-english speakers had the audacity
to rewrite the dictionary and continue to call it English!
I will never write colour without a u, ever! I may suffer the global
American cultural invasion of my country like the rest of us, but I will
never let them infiltrate my mind! ;)


May 28, 2013
On 5/27/2013 9:27 PM, Manu wrote:
> I will never write colour without a u, ever! I may suffer the global American
> cultural invasion of my country like the rest of us, but I will never let them
> infiltrate my mind! ;)

Resistance is useless.
May 28, 2013
On Tuesday, 28 May 2013 at 04:52:55 UTC, Walter Bright wrote:
> On 5/27/2013 9:27 PM, Manu wrote:
>> I will never write colour without a u, ever! I may suffer the global American
>> cultural invasion of my country like the rest of us, but I will never let them
>> infiltrate my mind! ;)
>
> Resistance is useless.

*futile :P
May 28, 2013
On 28/05/13 13:22, David Eagen wrote:
> On Tuesday, 28 May 2013 at 01:38:22 UTC, Peter Williams wrote:
>
>>
>> So you're going to spell check them all to make sure that they're
>> English?  Or did you mean ASCII?
>>
>> Peter
>
> That's it. I'm filing a bug against std.traits. There's a unittest there
> that with a struct named "Colour". Completely unacceptable.

Except here in Australia and other places where they use the Queen's English :-)

Peter
May 28, 2013
On 28 May 2013 14:38, Peter Williams <pwil3058@bigpond.net.au> wrote:

> On 28/05/13 13:22, David Eagen wrote:
>
>> On Tuesday, 28 May 2013 at 01:38:22 UTC, Peter Williams wrote:
>>
>>
>>> So you're going to spell check them all to make sure that they're English?  Or did you mean ASCII?
>>>
>>> Peter
>>>
>>
>> That's it. I'm filing a bug against std.traits. There's a unittest there that with a struct named "Colour". Completely unacceptable.
>>
>
> Except here in Australia and other places where they use the Queen's English :-)


Is there anywhere other than America that doesn't?