On Tuesday, 28 May 2013 at 00:11:18 UTC, Walter Bright wrote:
Every time I've been to a programming shop in a foreign
country, the developers speak english at work and code in
english. Of course, that doesn't mean that everyone does, but
as far as I can tell the overwhelming bulk is done in eng
On Thursday, 30 May 2013 at 11:29:47 UTC, Manu wrote:
Have you ever worked on code written by people who barely speak
English?
I did. It's better than having a mixture of languages like here:
http://code.google.com/p/trileri/source/browse/trunk/tr/yazi.d
assert(length == dizgi.length); - in o
On Jun 17, 2013, at 6:28 PM, Brad Roberts wrote:
> On 6/17/13 11:58 AM, Sean Kelly wrote:
>> On Jun 17, 2013, at 11:47 AM, "H. S. Teoh" wrote:
>>>
>>> Do linkers actually support 8-bit symbol names? Or do these have to be
>>> translated into ASCII somehow?
>>
>> Good question. It looks like t
On Tue, Jun 18, 2013 at 04:33:54PM -0700, Walter Bright wrote:
> On 6/18/2013 9:44 AM, H. S. Teoh wrote:
> >Might this cause a problem with the VS linker?
>
> I doubt it, but try it and see!
Sadly I don't have access to a Windows dev machine. Anybody else cares
to try?
T
--
Study gravitation,
On 6/18/2013 9:44 AM, H. S. Teoh wrote:
Might this cause a problem with the VS linker?
I doubt it, but try it and see!
On Mon, Jun 17, 2013 at 06:49:19PM -0700, Walter Bright wrote:
> On 6/17/2013 6:28 PM, Brad Roberts wrote:
> >Don't symbol names from dmd/win32 get compressed if they're too long,
> >resulting
> >in essentially arbitrary random binary data being used as symbol names?
> >Assuming my memory on that
On 6/17/2013 6:28 PM, Brad Roberts wrote:
Don't symbol names from dmd/win32 get compressed if they're too long, resulting
in essentially arbitrary random binary data being used as symbol names?
Assuming my memory on that is correct then it's already demonstrated that
optlink doesn't care what the
On 6/17/13 11:58 AM, Sean Kelly wrote:
On Jun 17, 2013, at 11:47 AM, "H. S. Teoh" wrote:
Do linkers actually support 8-bit symbol names? Or do these have to be
translated into ASCII somehow?
Good question. It looks like the linker on OSX does:
public _D3abc1A18さいごの果実MFiZv
On 05/31/2013 05:11 AM, Simen Kjaeraas wrote:
On Fri, 31 May 2013 07:57:37 +0200, Walter Bright
wrote:
On 5/30/2013 5:00 PM, Peter Williams wrote:
On 31/05/13 05:07, Walter Bright wrote:
On 5/30/2013 4:24 AM, Manu wrote:
We don't all know English. Plenty of people don't.
I've worked a lot w
On Jun 17, 2013, at 11:47 AM, "H. S. Teoh" wrote:
>
> Do linkers actually support 8-bit symbol names? Or do these have to be
> translated into ASCII somehow?
Good question. It looks like the linker on OSX does:
public _D3abc1A18さいごの果実MFiZv
public _D3abc1A4ªåMFiZv
The object
On Mon, Jun 17, 2013 at 11:37:18AM -0700, Sean Kelly wrote:
> On Jun 5, 2013, at 6:21 PM, Brad Roberts wrote:
>
> > On 6/5/13 6:11 PM, Timothee Cour wrote:
> >> currently std.demangle.demangle doesn't work with unicode (see example
> >> below)
> >>
> >> If we decide to keep allowing unicode sym
On Jun 5, 2013, at 6:21 PM, Brad Roberts wrote:
> On 6/5/13 6:11 PM, Timothee Cour wrote:
>> currently std.demangle.demangle doesn't work with unicode (see example below)
>>
>> If we decide to keep allowing unicode symbols (as opposed to just unicode
>> strings/comments), we must
>> address thi
On 6/5/13 6:11 PM, Timothee Cour wrote:
currently std.demangle.demangle doesn't work with unicode (see example below)
If we decide to keep allowing unicode symbols (as opposed to just unicode
strings/comments), we must
address this issue. Will supporting this negatively impact performance (of b
On Thu, May 30, 2013 at 10:57 PM, Walter Bright
wrote:
> On 5/30/2013 5:00 PM, Peter Williams wrote:
>
>> On 31/05/13 05:07, Walter Bright wrote:
>>
>>> On 5/30/2013 4:24 AM, Manu wrote:
>>>
We don't all know English. Plenty of people don't.
I've worked a lot with Sony and Nintendo code/
On Fri, 31 May 2013 07:57:37 +0200, Walter Bright
wrote:
On 5/30/2013 5:00 PM, Peter Williams wrote:
On 31/05/13 05:07, Walter Bright wrote:
On 5/30/2013 4:24 AM, Manu wrote:
We don't all know English. Plenty of people don't.
I've worked a lot with Sony and Nintendo code/libraries, for ins
On 5/30/2013 5:04 PM, Manu wrote:
Currently, D offers a unique advantage; leave it that way.
I am going to leave it that way based on the comments here, I only wanted to
point out that the example didn't support Unicode identifiers.
On 5/30/2013 5:00 PM, Peter Williams wrote:
On 31/05/13 05:07, Walter Bright wrote:
On 5/30/2013 4:24 AM, Manu wrote:
We don't all know English. Plenty of people don't.
I've worked a lot with Sony and Nintendo code/libraries, for instance,
it almost
always looks like this:
{
// E: I like ca
On 31 May 2013 10:00, Peter Williams wrote:
> On 31/05/13 05:07, Walter Bright wrote:
>
>> On 5/30/2013 4:24 AM, Manu wrote:
>>
>>> We don't all know English. Plenty of people don't.
>>> I've worked a lot with Sony and Nintendo code/libraries, for instance,
>>> it almost
>>> always looks like thi
On 31 May 2013 03:08, Entry wrote:
> On Thursday, 30 May 2013 at 16:05:13 UTC, Jakob Ovrum wrote:
>
>> On Thursday, 30 May 2013 at 15:48:12 UTC, Entry wrote:
>>
>>> I'm glad you agree, though I believe that I never said anything about D
>>> 'choosing' which human languages are compatible with it.
On 31 May 2013 01:48, Entry wrote:
> On Thursday, 30 May 2013 at 14:49:12 UTC, monarch_dodra wrote:
>
>> On Thursday, 30 May 2013 at 14:13:47 UTC, Entry wrote:
>>
>>> Take a minute to think about why we're all communicating in English
>>> here. Let's see if you can figure it out.
>>>
>>
>> Well t
On 31 May 2013 05:07, Walter Bright wrote:
> On 5/30/2013 4:24 AM, Manu wrote:
>
>> We don't all know English. Plenty of people don't.
>> I've worked a lot with Sony and Nintendo code/libraries, for instance, it
>> almost
>> always looks like this:
>>
>> {
>>// E: I like cake.
>>// J: ケーキ
On 31/05/13 05:07, Walter Bright wrote:
On 5/30/2013 4:24 AM, Manu wrote:
We don't all know English. Plenty of people don't.
I've worked a lot with Sony and Nintendo code/libraries, for instance,
it almost
always looks like this:
{
// E: I like cake.
// J: ケーキが好きです。
player.eatCake();
}
Am Thu, 30 May 2013 09:19:32 +0200
schrieb "Joakim" :
> Your point is? 121 results, including false positives like
> "utf-8 is the best guess." If you look at the results, almost
> all make the pragmatic recommendation that UTF-8 is the best _for
> now_, because it is better supported than other
On 5/30/2013 4:24 AM, Manu wrote:
We don't all know English. Plenty of people don't.
I've worked a lot with Sony and Nintendo code/libraries, for instance, it almost
always looks like this:
{
// E: I like cake.
// J: ケーキが好きです。
player.eatCake();
}
Clearly someone doesn't speak English i
On Thursday, 30 May 2013 at 16:05:13 UTC, Jakob Ovrum wrote:
On Thursday, 30 May 2013 at 15:48:12 UTC, Entry wrote:
I'm glad you agree, though I believe that I never said
anything about D 'choosing' which human languages are
compatible with it. I just expressed my belief that should
people cho
On Thursday, 30 May 2013 at 15:48:12 UTC, Entry wrote:
I'm glad you agree, though I believe that I never said anything
about D 'choosing' which human languages are compatible with
it. I just expressed my belief that should people choose to
construct something, be it a ship or a computer program
On Thursday, 30 May 2013 at 14:49:12 UTC, monarch_dodra wrote:
On Thursday, 30 May 2013 at 14:13:47 UTC, Entry wrote:
Take a minute to think about why we're all communicating in
English here. Let's see if you can figure it out.
Well that's condescending :/ and fallacious.
To answer your quest
On Wednesday, 29 May 2013 at 22:44:17 UTC, Walter Bright wrote:
(Also note that I meant using ASCII, not necessarily english.)
I don't understand the logic behind this. Surely this is the
worst combination; severely crippled ability to use non-English
languages (yes, even for European languag
On Thursday, 30 May 2013 at 14:13:47 UTC, Entry wrote:
Take a minute to think about why we're all communicating in
English here. Let's see if you can figure it out.
Well that's condescending :/ and fallacious.
To answer your question, it may have something to do with the
fact that these are t
On Thursday, 30 May 2013 at 13:52:09 UTC, monarch_dodra wrote:
On Thursday, 30 May 2013 at 13:12:17 UTC, Entry wrote:
On Thursday, 30 May 2013 at 09:29:43 UTC, monarch_dodra wrote:
On Thursday, 30 May 2013 at 08:32:01 UTC, Entry wrote:
On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams
On Thursday, 30 May 2013 at 13:12:17 UTC, Entry wrote:
On Thursday, 30 May 2013 at 09:29:43 UTC, monarch_dodra wrote:
On Thursday, 30 May 2013 at 08:32:01 UTC, Entry wrote:
On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams
wrote:
On 30/05/13 08:40, Entry wrote:
My personal opinion is
On Thursday, 30 May 2013 at 09:29:43 UTC, monarch_dodra wrote:
On Thursday, 30 May 2013 at 08:32:01 UTC, Entry wrote:
On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams
wrote:
On 30/05/13 08:40, Entry wrote:
My personal opinion is that code should only be in English.
But why would you
On Thursday, 30 May 2013 at 11:29:47 UTC, Manu wrote:
Have you ever worked on code written by people who barely speak
English?
Even if they write English words, that doesn't make it
'English', or any
easier to understand. And people often tend to just
transliterate into
latin, which is kinda p
On 30 May 2013 20:13, Dicebot wrote:
> On Thursday, 30 May 2013 at 09:36:43 UTC, monarch_dodra wrote:
>
>> What about Chinese? Russian? Japanese? It is doable, but I can tell you
>> for a fact that they very much don't like reading it that way.
>>
>> You know, having done programming in Japan, I
On 30 May 2013 18:32, Entry wrote:
> On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams wrote:
>
>> On 30/05/13 08:40, Entry wrote:
>>
>>> My personal opinion is that code should only be in English.
>>>
>>
>> But why would you want to impose this restriction on others?
>>
>> Peter
>>
>
> I
On 30 May 2013 18:32, Entry wrote:
> On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams wrote:
>
>> On 30/05/13 08:40, Entry wrote:
>>
>>> My personal opinion is that code should only be in English.
>>>
>>
>> But why would you want to impose this restriction on others?
>>
>> Peter
>>
>
> I
On 05/29/2013 12:03 PM, Marco Leise wrote:
... And everyone
likes "alias ℕ = size_t;", right? :)
...
No, that's deeply troubling.
On Thursday, 30 May 2013 at 10:13:46 UTC, Dicebot wrote:
On Thursday, 30 May 2013 at 09:36:43 UTC, monarch_dodra wrote:
What about Chinese? Russian? Japanese? It is doable, but I can
tell you for a fact that they very much don't like reading it
that way.
You know, having done programming in J
On Thursday, 30 May 2013 at 09:36:43 UTC, monarch_dodra wrote:
What about Chinese? Russian? Japanese? It is doable, but I can
tell you for a fact that they very much don't like reading it
that way.
You know, having done programming in Japan, I know that a lot
of devs simply don't care for eng
On Thu, 30 May 2013 11:36:42 +0200, monarch_dodra
wrote:
On Wednesday, 29 May 2013 at 22:42:08 UTC, Walter Bright wrote:
On 5/29/2013 3:26 AM, qznc wrote:
Once I heared an argument from developers working for banks. They coded
business-specific stuff in Java. Business-specific meant financi
On Wednesday, 29 May 2013 at 22:42:08 UTC, Walter Bright wrote:
On 5/29/2013 3:26 AM, qznc wrote:
Once I heared an argument from developers working for banks.
They coded
business-specific stuff in Java. Business-specific meant
financial concepts with
german names (e.g. Vermögen,Bürgschaft), whi
On Thursday, 30 May 2013 at 08:32:01 UTC, Entry wrote:
On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams wrote:
On 30/05/13 08:40, Entry wrote:
My personal opinion is that code should only be in English.
But why would you want to impose this restriction on others?
Peter
I wouldn't
On Wednesday, 29 May 2013 at 23:57:01 UTC, Peter Williams wrote:
On 30/05/13 08:40, Entry wrote:
My personal opinion is that code should only be in English.
But why would you want to impose this restriction on others?
Peter
I wouldn't say impose. I'd say that programming in a unified
langu
On Wednesday, 29 May 2013 at 23:40:51 UTC, Marco Leise wrote:
Am Sun, 26 May 2013 21:25:36 +0200
schrieb "Joakim" :
On Sunday, 26 May 2013 at 19:11:42 UTC, Mr. Anonymous wrote:
> On Sunday, 26 May 2013 at 19:05:32 UTC, Joakim wrote:
>> On Sunday, 26 May 2013 at 18:29:38 UTC, Andrei Alexandrescu
On Wednesday, 29 May 2013 at 22:44:17 UTC, Walter Bright wrote:
I still think it's a bad idea, but it's obvious people want it
in D, so it'll stay.
(Also note that I meant using ASCII, not necessarily english.)
Good, thanks, restrictions definetelly can and should be applied
per project, l
On 30/05/13 08:40, Entry wrote:
My personal opinion is that code should only be in English.
But why would you want to impose this restriction on others?
Peter
Am Sun, 26 May 2013 21:25:36 +0200
schrieb "Joakim" :
> On Sunday, 26 May 2013 at 19:11:42 UTC, Mr. Anonymous wrote:
> > On Sunday, 26 May 2013 at 19:05:32 UTC, Joakim wrote:
> >> On Sunday, 26 May 2013 at 18:29:38 UTC, Andrei Alexandrescu
> >> wrote:
> >>> On 5/26/13 1:45 PM, Joakim wrote:
> >>>
Am Wed, 29 May 2013 15:44:17 -0700
schrieb Walter Bright :
> I still think it's a bad idea, but it's obvious people want it in D, so it'll
> stay.
>
> (Also note that I meant using ASCII, not necessarily english.)
Surprisingly ASCII also covers Cornish and Malay.
--
Marco
On 5/29/2013 2:42 AM, Jakob Ovrum wrote:
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
I've recently come to the opinion that that's a bad idea, and D should not
support it.
Honestly, removing support for non-ASCII characters from identifiers is the
worst idea you've had in a wh
On 5/29/2013 3:26 AM, qznc wrote:
Once I heared an argument from developers working for banks. They coded
business-specific stuff in Java. Business-specific meant financial concepts with
german names (e.g. Vermögen,Bürgschaft), which sometimes include äöüß. Some of
those concept had no good trans
My personal opinion is that code should only be in English.
On Tuesday, 28 May 2013 at 00:11:18 UTC, Walter Bright wrote:
On 5/27/2013 4:28 PM, Hans W. Uhlig wrote:
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
I've recently come to the opinion that that's a bad idea, and
D should not
support it.
Why do you think its a bad idea? It mak
On Tuesday, 28 May 2013 at 01:17:37 UTC, H. S. Teoh wrote:
On Tue, May 28, 2013 at 02:54:30AM +0200, Torje Digernes wrote:
On Tuesday, 28 May 2013 at 00:34:20 UTC, Manu wrote:
>On 28 May 2013 09:05, Walter Bright
>
>wrote:
>
>>On 5/27/2013 3:18 PM, H. S. Teoh wrote:
>>
>>>Well, D *does* suppor
Am Mon, 27 May 2013 16:05:46 -0700
schrieb Walter Bright :
> 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)
> >
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
I've recently come to the opinion that that's a bad idea, and D
should not support it.
Honestly, removing support for non-ASCII characters from
identifiers is the worst idea you've had in a while. There is an
_unfathomable amount_ o
On Wednesday, 29 May 2013 at 01:29:07 UTC, Diggory wrote:
On Tuesday, 28 May 2013 at 23:33:47 UTC, Peter Williams wrote:
On 28/05/13 19:12, Jacob Carlborg wrote:
On 2013-05-28 08:00, Manu wrote:
Is there anywhere other than America that doesn't?
Canada, Jamaica, other countries in that regi
On Wed, May 29, 2013 at 10:36:08AM +1000, Peter Williams wrote:
> On 29/05/13 09:57, H. S. Teoh wrote:
> >On Wed, May 29, 2013 at 09:33:32AM +1000, Peter Williams wrote:
> >>On 28/05/13 19:12, Jacob Carlborg wrote:
> >>>On 2013-05-28 08:00, Manu wrote:
> >>>
> Is there anywhere other than Ameri
On Tuesday, 28 May 2013 at 23:33:47 UTC, Peter Williams wrote:
On 28/05/13 19:12, Jacob Carlborg wrote:
On 2013-05-28 08:00, Manu wrote:
Is there anywhere other than America that doesn't?
Canada, Jamaica, other countries in that region?
Last time I looked Canada was in America (which is a
On 29/05/13 09:57, H. S. Teoh wrote:
On Wed, May 29, 2013 at 09:33:32AM +1000, Peter Williams wrote:
On 28/05/13 19:12, Jacob Carlborg wrote:
On 2013-05-28 08:00, Manu wrote:
Is there anywhere other than America that doesn't?
Canada, Jamaica, other countries in that region?
Last time I l
On Wed, May 29, 2013 at 09:33:32AM +1000, Peter Williams wrote:
> On 28/05/13 19:12, Jacob Carlborg wrote:
> >On 2013-05-28 08:00, Manu wrote:
> >
> >>Is there anywhere other than America that doesn't?
> >
> >Canada, Jamaica, other countries in that region?
> >
>
> Last time I looked Canada was in
On 28/05/13 19:12, Jacob Carlborg wrote:
On 2013-05-28 08:00, Manu wrote:
Is there anywhere other than America that doesn't?
Canada, Jamaica, other countries in that region?
Last time I looked Canada was in America (which is a continent not a
country). :-)
Peter
On 2013-05-28 01:34:17 +, Walter Bright said:
On 5/27/2013 6:06 PM, H. S. Teoh wrote:
I don't find this a compelling reason to allow full Unicode on
identifiers, though. For one thing, somebody maintaining your code may
not know how to type said identifier correctly. It can be very
frustra
On 2013-05-28 14:58, Simen Kjaeraas wrote:
America is not a country. The country is called USA.
I know that, but I get the impression that people usually say "America"
and refer to USA.
--
/Jacob Carlborg
On Tue, 28 May 2013 01:05:46 +0200, Walter Bright
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)
On Tue, 28 May 2013 14:11:29 +0200, Jacob Carlborg wrote:
On 2013-05-28 14:09, Manu wrote:
Yes, the region called America ;)
Although there's a few British colonies in the Caribbean...
Oh, you meant the whole region and not the country.
America is not a country. The country is called USA.
On 2013-05-28 14:09, Manu wrote:
Yes, the region called America ;)
Although there's a few British colonies in the Caribbean...
Oh, you meant the whole region and not the country.
--
/Jacob Carlborg
On 28 May 2013 19:12, Jacob Carlborg wrote:
> On 2013-05-28 08:00, Manu wrote:
>
> Is there anywhere other than America that doesn't?
>>
>
> Canada, Jamaica, other countries in that region?
Yes, the region called America ;)
Although there's a few British colonies in the Caribbean...
On Monday, 27 May 2013 at 22:20:16 UTC, H. S. Teoh wrote:
On Tue, May 28, 2013 at 12:04:52AM +0200, Vladimir Panteleev
wrote:
On Monday, 27 May 2013 at 21:24:15 UTC, H. S. Teoh wrote:
>Besides, it's impractical to use compose key sequences to
>write
>large amounts of text in some given languag
On Tuesday, 28 May 2013 at 00:11:18 UTC, Walter Bright wrote:
Every time I've been to a programming shop in a foreign
country, the developers speak english at work and code in
english. Of course, that doesn't mean that everyone does, but
as far as I can tell the overwhelming bulk is done in eng
On Monday, 27 May 2013 at 23:46:17 UTC, H. S. Teoh wrote:
On Tue, May 28, 2013 at 01:28:22AM +0200, Hans W. Uhlig wrote:
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
>On 5/27/2013 3:18 PM, H. S. Teoh wrote:
>>Well, D *does* support non-English identifiers, y'know... for
>>example
On Tuesday, 28 May 2013 at 01:34:47 UTC, Walter Bright wrote:
Why? You said previously that you'd love to support extended
operators ;)
Extended operators, yes. Non-ascii identifiers, no.
BTW, this is one of big D advantage, take into account
some day D could be used for teaching in schools
On 2013-05-28 08:00, Manu wrote:
Is there anywhere other than America that doesn't?
Canada, Jamaica, other countries in that region?
--
/Jacob Carlborg
On 2013-05-28 03:38, Peter Williams wrote:
So you're going to spell check them all to make sure that they're
English? Or did you mean ASCII?
Don't you have a spell checker in your editor? If not, find a new one :)
--
/Jacob Carlborg
On Tuesday, 28 May 2013 at 00:11:18 UTC, Walter Bright wrote:
Every time I've been to a programming shop in a foreign
country, the developers speak english at work and code in
english. Of course, that doesn't mean that everyone does, but
as far as I can tell the overwhelming bulk is done in e
On 28 May 2013 14:38, Peter Williams 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 i
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
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 us
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.
On 28 May 2013 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 unitt
On 28 May 2013 11:42, Jonathan M Davis 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 ch
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
u
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 y
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
On 5/27/2013 6:06 PM, H. S. Teoh wrote:
I don't find this a compelling reason to allow full Unicode on
identifiers, though. For one thing, somebody maintaining your code may
not know how to type said identifier correctly. It can be very
frustrating to have to keep copy-n-pasting identifiers just
On 5/27/2013 5:34 PM, Manu wrote:
On 28 May 2013 09:05, Walter Bright mailto:newshou...@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) {
On Tue, May 28, 2013 at 02:54:30AM +0200, Torje Digernes wrote:
> On Tuesday, 28 May 2013 at 00:34:20 UTC, Manu wrote:
> >On 28 May 2013 09:05, Walter Bright
> >wrote:
> >
> >>On 5/27/2013 3:18 PM, H. S. Teoh wrote:
> >>
> >>>Well, D *does* support non-English identifiers, y'know... for
> >>>examp
On Tue, May 28, 2013 at 02:23:32AM +0200, Diggory wrote:
> On Tuesday, 28 May 2013 at 00:11:18 UTC, Walter Bright wrote:
> >On 5/27/2013 4:28 PM, Hans W. Uhlig wrote:
> >>On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
> >>>I've recently come to the opinion that that's a bad idea, and
On Tuesday, 28 May 2013 at 00:34:20 UTC, Manu wrote:
On 28 May 2013 09:05, Walter Bright
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;
On 28 May 2013 09:39, "@puremagic.com <
"\"Luís".Marques"> wrote:
> On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
>
>> I've recently come to the opinion that that's a bad idea, and D should
>> not support it.
>>
>
> I think it is a bad idea to program in a language other than englis
On 28 May 2013 09:05, Walter Bright 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)
>>
On Tuesday, 28 May 2013 at 00:11:18 UTC, Walter Bright wrote:
On 5/27/2013 4:28 PM, Hans W. Uhlig wrote:
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
I've recently come to the opinion that that's a bad idea, and
D should not
support it.
Why do you think its a bad idea? It mak
On 5/27/2013 4:28 PM, Hans W. Uhlig wrote:
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
I've recently come to the opinion that that's a bad idea, and D should not
support it.
Why do you think its a bad idea? It makes it such that code can be in various
languages? Just lack of k
On Tue, May 28, 2013 at 01:28:22AM +0200, Hans W. Uhlig wrote:
> On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright 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) {
> >>
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright wrote:
I've recently come to the opinion that that's a bad idea, and D
should not support it.
I think it is a bad idea to program in a language other than
english, but I believe D should still support it.
On Monday, 27 May 2013 at 23:05:46 UTC, Walter Bright 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)
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 c
On Tue, 28 May 2013 00:18:31 +0200, H. S. Teoh
wrote:
On Tue, May 28, 2013 at 12:04:52AM +0200, Vladimir Panteleev wrote:
On Monday, 27 May 2013 at 21:24:15 UTC, H. S. Teoh wrote:
>Besides, it's impractical to use compose key sequences to write
>large amounts of text in some given language;
On Tue, May 28, 2013 at 12:04:52AM +0200, Vladimir Panteleev wrote:
> On Monday, 27 May 2013 at 21:24:15 UTC, H. S. Teoh wrote:
> >Besides, it's impractical to use compose key sequences to write
> >large amounts of text in some given language; a method of
> >temporarily switching to a different lay
On Monday, 27 May 2013 at 21:24:15 UTC, H. S. Teoh wrote:
Besides, it's impractical to use compose key sequences to write
large amounts of text in some given language; a method of
temporarily switching to a different layout is necessary.
I thought the topic was typing the occasional Unicode ch
On Mon, May 27, 2013 at 09:59:52PM +0200, Vladimir Panteleev wrote:
> On Monday, 27 May 2013 at 02:17:08 UTC, Wyatt wrote:
> >No hardware required; just a smarter IME.
>
> Perhaps something like the compose key?
>
> http://en.wikipedia.org/wiki/Compose_key
I'm already using the compose key. But
1 - 100 of 196 matches
Mail list logo
