On Saturday, 29 September 2018 at 16:19:38 UTC, ag0aep6g wrote:
On 09/29/2018 04:19 PM, Shachar Shemesh wrote:
On 29/09/18 16:52, Dukc wrote:
[...]
I know you meant Sarn, but still... can you please be a bit
less aggresive with our wording?
From the article (the furthest point I read in
On 09/29/2018 04:19 PM, Shachar Shemesh wrote:
On 29/09/18 16:52, Dukc wrote:
[...]
I know you meant Sarn, but still... can you please be a bit less
aggresive with our wording?
From the article (the furthest point I read in it):
When I ask myself what I've found life is too short for, the
On 29/09/18 16:52, Dukc wrote:
On Saturday, 29 September 2018 at 02:22:55 UTC, Shachar Shemesh wrote:
I missed something he said in one of the other (as of this writing,
98) posts of this thread, and thus causing Dukc to label me a
bullshitter.
I know you meant Sarn, but still... can you
On Saturday, 29 September 2018 at 02:22:55 UTC, Shachar Shemesh
wrote:
I missed something he said in one of the other (as of this
writing, 98) posts of this thread, and thus causing Dukc to
label me a bullshitter.
I know you meant Sarn, but still... can you please be a bit less
aggresive
On 28/09/18 14:37, Dukc wrote:
On Friday, 28 September 2018 at 02:23:32 UTC, sarn wrote:
Shachar seems to be aiming for an internet high score by shooting down
threads without reading them. You have better things to do.
http://www.paulgraham.com/vb.html
I believe you're being too harsh.
On Friday, 28 September 2018 at 11:37:10 UTC, Dukc wrote:
It's easy to miss a part of a post sometimes.
That's very true, and it's always good to give people the benefit
of the doubt. But most people are able to post constructively
here without
* Abrasively and condescendingly declaring
On Friday, 28 September 2018 at 02:23:32 UTC, sarn wrote:
Shachar seems to be aiming for an internet high score by
shooting down threads without reading them. You have better
things to do.
http://www.paulgraham.com/vb.html
I believe you're being too harsh. It's easy to miss a part of a
On Thursday, 27 September 2018 at 16:34:37 UTC, aliak wrote:
On Thursday, 27 September 2018 at 13:59:48 UTC, Shachar Shemesh
wrote:
On 27/09/18 16:38, aliak wrote:
The point was that being able to use non-English in code is
demonstrably both helpful and useful to people. Norwegian
happens to
On Thursday, 27 September 2018 at 13:59:48 UTC, Shachar Shemesh
wrote:
On 27/09/18 16:38, aliak wrote:
The point was that being able to use non-English in code is
demonstrably both helpful and useful to people. Norwegian
happens to be easily anglicize-able. I've already linked to
non ascii
On 27/09/18 16:38, aliak wrote:
The point was that being able to use non-English in code is demonstrably
both helpful and useful to people. Norwegian happens to be easily
anglicize-able. I've already linked to non ascii code versions in a
previous post if you want that too.
If you wish to
On Thursday, 27 September 2018 at 08:16:00 UTC, Shachar Shemesh
wrote:
On 27/09/18 10:35, aliak wrote:
Here's an example from this years spring semester and NTNU
(norwegian uni):
http://folk.ntnu.no/frh/grprog/eksempel/eks_20.cpp
... That's the basic programming course. Whether the professor
On 9/27/2018 12:35 AM, aliak wrote:
Anyway, on a related note: D itself (not identifiers, but std) also supports
unicode 6 or something. That's from 2010. That's a decade ago. We're at unicode
11 now. And I've already had someone tell me (while trying to get them to use D)
- "hold on it
On 27/09/18 10:35, aliak wrote:
Here's an example from this years spring semester and NTNU (norwegian
uni): http://folk.ntnu.no/frh/grprog/eksempel/eks_20.cpp
... That's the basic programming course. Whether the professor would use
that I guess would depend on ratio of English/non-English
On Wednesday, 26 September 2018 at 20:43:47 UTC, Walter Bright
wrote:
On 9/26/2018 5:46 AM, Steven Schveighoffer wrote:
This is a non-starter. We can't break people's code,
especially for trivial reasons like 'you shouldn't code that
way because others don't like it'. I'm pretty sure Walter
On Sunday, September 23, 2018 2:49:39 PM MDT Walter Bright via Digitalmars-d
wrote:
> There's a reason why dmd doesn't have international error messages. My
> experience with it is that international users don't want it. They prefer
> the english messages.
It reminds me of one of the reasons
On 09/26/2018 01:43 PM, Walter Bright wrote:
Don't most languages have a Romanji-like
representation?
Yes, a lot of languages that don't use the Latin alphabet have standard
transcriptions into the Latin alphabet. Standard transcriptions into
ASCII are much less common, and newer Unicode
On 9/26/18 4:43 PM, Walter Bright wrote:
But expanding it seems of vanishingly little value. Note that each thing
that gets added to D adds weight to it, and it needs to pull its weight.
Nothing is free.
It may be the weight is already there in the form of unicode symbol
support, just the
On Wednesday, 26 September 2018 at 20:43:47 UTC, Walter Bright
wrote:
I don't see a scenario where someone would be learning D and
not know English. Non-English D instructional material is
nearly non-existent.
http://ddili.org/ders/d/
On 9/26/2018 5:46 AM, Steven Schveighoffer wrote:
Does this need a DIP?
Feel free to write one, but its chances of getting incorporated are remote and
would require a pretty strong rationale that I haven't seen yet.
On 9/26/2018 5:46 AM, Steven Schveighoffer wrote:
This is a non-starter. We can't break people's code, especially for trivial
reasons like 'you shouldn't code that way because others don't like it'. I'm
pretty sure Walter would be against removing Unicode support for identifiers.
We're not
On 9/25/2018 11:50 PM, Shachar Shemesh wrote:
This sounded like a very compelling example, until I gave it a second thought. I
now fail to see how this example translates to a real-life scenario.
Also, there are usually common ASCII versions of city names, such as Cologne for
Köln.
On Sunday, 23 September 2018 at 20:49:39 UTC, Walter Bright wrote:
On 9/23/2018 9:52 AM, aliak wrote:
There's a reason why dmd doesn't have international error
messages. My experience with it is that international users
don't want it. They prefer the english messages.
Yes please. Keep them
On 9/26/18 5:54 AM, rjframe wrote:
On Fri, 21 Sep 2018 16:27:46 +, Neia Neutuladh wrote:
I've got this coded up and can submit a PR, but I thought I'd get
feedback here first.
Does anyone see any horrible potential problems here?
Or is there an interestingly better option?
Does this
On 9/26/18 2:50 AM, Shachar Shemesh wrote:
On 25/09/18 15:35, Dukc wrote:
Another reason is that something may not have a good translation to
English. If there is an enum type listing city names, it is IMO better
to write them as normal, using Unicode. CityName.seinäjoki, not
On Fri, 21 Sep 2018 16:27:46 +, Neia Neutuladh wrote:
> I've got this coded up and can submit a PR, but I thought I'd get
> feedback here first.
>
> Does anyone see any horrible potential problems here?
>
> Or is there an interestingly better option?
>
> Does this need a DIP?
I just want
On Wednesday, 26 September 2018 at 07:37:28 UTC, Shachar Shemesh
wrote:
The other type of answer is "it's being done in the real
world". If it's in active use in the real world, it might make
sense to support it, even if we can agree that the design is
not optimal.
Shachar
Two years ago, I
On 26/09/18 10:26, Dukc wrote:
On Wednesday, 26 September 2018 at 06:50:47 UTC, Shachar Shemesh wrote:
The properties that cause city names to be poor candidates for enum
values are the same as those that make them Unicode candidates.
How so?
City names (data, changes over time) as enums
On Wednesday, 26 September 2018 at 06:50:47 UTC, Shachar Shemesh
wrote:
The properties that cause city names to be poor candidates for
enum values are the same as those that make them Unicode
candidates.
How so?
City names (data, changes over time) as enums (compile time
set) seem like a
On 25/09/18 15:35, Dukc wrote:
Another reason is that something may not have a good translation to
English. If there is an enum type listing city names, it is IMO better
to write them as normal, using Unicode. CityName.seinäjoki, not
CityName.seinaejoki.
This sounded like a very compelling
On 2018-09-21 18:27, Neia Neutuladh wrote:
D's currently accepted identifier characters are based on Unicode 2.0:
* ASCII range values are handled specially.
* Letters and combining marks from Unicode 2.0 are accepted.
* Numbers outside the ASCII range are accepted.
* Eight random punctuation
When I make code that I expect to be only used around here, I
generally write the code itself in english but comments in my own
language. I agree that in general, it's better to stick with
english in identifiers when the programming language and the
standard library is English.
On Tuesday,
On Friday, 21 September 2018 at 23:17:42 UTC, Seb wrote:
In all seriousness I hate it when someone thought its funny to
use the lambda symbol as an identifier and I have to copy that
symbol whenever I want to use it because there's no convenient
way to type it.
(This is already supported in
On 9/23/2018 12:06 PM, Abdulhaq wrote:
The early history of computer science is completely dominated by cultures who
use latin script based characters,
Small character sets are much more implementable on primitive systems like
telegraphs and electro-mechanical ttys.
It wasn't even practical
On 9/24/18 3:18 PM, Patrick Schluter wrote:
On Monday, 24 September 2018 at 13:26:14 UTC, Steven Schveighoffer wrote:
2. There are no rules about what *encoding* is acceptable, it's
implementation defined. So various compilers have different rules as
to what will be accepted in the actual
On Monday, 24 September 2018 at 13:26:14 UTC, Steven
Schveighoffer wrote:
2. There are no rules about what *encoding* is acceptable, it's
implementation defined. So various compilers have different
rules as to what will be accepted in the actual source code. In
fact, I read somewhere that not
On 9/24/18 2:20 PM, Martin Tschierschke wrote:
On Monday, 24 September 2018 at 14:34:21 UTC, Steven Schveighoffer wrote:
On 9/24/18 10:14 AM, Adam D. Ruppe wrote:
On Monday, 24 September 2018 at 13:26:14 UTC, Steven Schveighoffer
wrote:
Part of the reason, which I haven't read here yet, is
On Monday, 24 September 2018 at 14:34:21 UTC, Steven
Schveighoffer wrote:
On 9/24/18 10:14 AM, Adam D. Ruppe wrote:
On Monday, 24 September 2018 at 13:26:14 UTC, Steven
Schveighoffer wrote:
Part of the reason, which I haven't read here yet, is that
all the keywords are in English.
Eh, those
On Monday, 24 September 2018 at 15:17:14 UTC, 0xEAB wrote:
Back then, when I coding C# in VS 2010 I was happy with the
German error messages.
addendum: I've been using the English version since VS2017
On Sunday, 23 September 2018 at 20:49:39 UTC, Walter Bright wrote:
There's a reason why dmd doesn't have international error
messages. My experience with it is that international users
don't want it. They prefer the english messages.
I'm a native German speaker.
As for my part, I agree on
On 9/24/18 10:14 AM, Adam D. Ruppe wrote:
On Monday, 24 September 2018 at 13:26:14 UTC, Steven Schveighoffer wrote:
Part of the reason, which I haven't read here yet, is that all the
keywords are in English.
Eh, those are kinda opaque sequences anyway, since the meanings aren't
quite what
On Monday, 24 September 2018 at 10:36:50 UTC, Jonathan M Davis
wrote:
Given that the typical keyboard has none of those characters,
maintaining code that used any of them would be a royal pain.
It is pretty easy to type them with a little keyboard config
change, and like vim can pick those up
On Monday, 24 September 2018 at 13:26:14 UTC, Steven
Schveighoffer wrote:
Part of the reason, which I haven't read here yet, is that all
the keywords are in English.
Eh, those are kinda opaque sequences anyway, since the meanings
aren't quite what the normal dictionary definition is anyway.
On 9/22/18 12:56 PM, Neia Neutuladh wrote:
On Saturday, 22 September 2018 at 12:35:27 UTC, Steven Schveighoffer wrote:
But aren't we arguing about the wrong thing here? D already accepts
non-ASCII identifiers.
Walter was doing that thing that people in the US who only speak English
tend to
On 9/24/18 12:23 AM, Neia Neutuladh wrote:
On Monday, 24 September 2018 at 01:39:43 UTC, Walter Bright wrote:
On 9/23/2018 3:23 PM, Neia Neutuladh wrote:
Okay, that's why you previously selected C99 as the standard for what
characters to allow. Do you want to update to match C11? It's been
On 9/22/18 8:58 AM, Jonathan M Davis wrote:
On Saturday, September 22, 2018 6:37:09 AM MDT Steven Schveighoffer via
Digitalmars-d wrote:
On 9/22/18 4:52 AM, Jonathan M Davis wrote:
I was laughing out loud when reading about composing "family"
emojis with zero-width joiners. If you told me that
On Monday, 24 September 2018 at 10:36:50 UTC, Jonathan M Davis
wrote:
Given that the typical keyboard has none of those characters,
maintaining code that used any of them would be a royal pain.
Note that I'm not trying to argue either way, it's just that I
used to think of Walter's stance on
On Monday, September 24, 2018 4:19:31 AM MDT Dennis via Digitalmars-d wrote:
> On Monday, 24 September 2018 at 01:32:38 UTC, Walter Bright wrote:
> > D the language is well suited to the development of Unicode
> > apps. D source code is another matter.
>
> But in the article you specifically talk
On Monday, 24 September 2018 at 01:32:38 UTC, Walter Bright wrote:
D the language is well suited to the development of Unicode
apps. D source code is another matter.
But in the article you specifically talk about the use of Unicode
in the context of source code instead of apps:
"With the D
On Monday, 24 September 2018 at 01:39:43 UTC, Walter Bright wrote:
On 9/23/2018 3:23 PM, Neia Neutuladh wrote:
Okay, that's why you previously selected C99 as the standard
for what characters to allow. Do you want to update to match
C11? It's been out for the better part of a decade, after
On 23/09/18 15:38, sarn wrote:
On Sunday, 23 September 2018 at 06:53:21 UTC, Shachar Shemesh wrote:
On 23/09/18 04:29, sarn wrote:
You can find a lot more Japanese D code on this blogging platform:
https://qiita.com/tags/dlang
Here's the most recent post to save you a click:
On 9/23/2018 3:23 PM, Neia Neutuladh wrote:
Okay, that's why you previously selected C99 as the standard for what characters
to allow. Do you want to update to match C11? It's been out for the better part
of a decade, after all.
I wasn't aware it changed in C11.
On 9/23/2018 6:06 PM, Dennis wrote:
Have you changed your mind since?
D the language is well suited to the development of Unicode apps. D source code
is another matter.
On Sunday, 23 September 2018 at 21:12:13 UTC, Walter Bright wrote:
D supports Unicode in identifiers because C and C++ do, and we
want to be able to interoperate with them. Extending Unicode
identifier support off into other directions, especially ones
that break such interoperability, is just
On Sunday, 23 September 2018 at 21:12:13 UTC, Walter Bright wrote:
D supports Unicode in identifiers because C and C++ do, and we
want to be able to interoperate with them. Extending Unicode
identifier support off into other directions, especially ones
that break such interoperability, is just
On 9/22/2018 6:01 PM, Jonathan M Davis wrote:
For better or worse, English is the international language of science and
engineering, and that includes programming.
In the earlier days of D, I put on the web pages a google widget what would
automatically translate the page into any language
On 9/23/2018 9:52 AM, aliak wrote:
Not seeing identifiers in languages you don't program in or can read in is
expected.
On the other hand, I've been programming for 40 years. I've customized my C++
compiler to emit error messages in various languages:
On Saturday, 22 September 2018 at 08:52:32 UTC, Jonathan M Davis
wrote:
Honestly, I was horrified to find out that emojis were even in
Unicode. It makes no sense whatsover. Emojis are supposed to be
sequences of characters that can be interepreted as images.
Treating them like Unicode
On Saturday, 22 September 2018 at 19:59:42 UTC, Erik van Velzen
wrote:
If there was a contingent of Japanese or Chinese users doing
that then surely they would speak up here or in Bugzilla to
advocate for this feature?
https://forum.dlang.org/post/piwvbtetcwyxlaloc...@forum.dlang.org
On Friday, 21 September 2018 at 20:25:54 UTC, Walter Bright wrote:
When I originally started with D, I thought non-ASCII
identifiers with Unicode was a good idea. I've since slowly
become less and less enthusiastic about it.
First off, D source text simply must (and does) fully support
On Sunday, 23 September 2018 at 06:53:21 UTC, Shachar Shemesh
wrote:
On 23/09/18 04:29, sarn wrote:
You can find a lot more Japanese D code on this blogging
platform:
https://qiita.com/tags/dlang
Here's the most recent post to save you a click:
On Sunday, 23 September 2018 at 11:18:42 UTC, Ali Çehreli wrote:
Hence, non-Unicode is unacceptable in Turkish code
You even contributed to
http://code.google.com/p/trileri/source/browse/trunk/tr/yazi.d
On Friday, 21 September 2018 at 23:17:42 UTC, Seb wrote:
A: Wait. Using emojis as identifiers is not a good idea?
B: Yes.
A: But the cool kids are doing it:
https://codepen.io/andresgalante/pen/jbGqXj
It's not like we have a lot of good fonts (I know only one), and
even fewer of them are
On 09/22/2018 09:27 AM, Neia Neutuladh wrote:
> Logographic writing systems. There is one logographic writing system
> still in common use, and it's the standard writing system for Chinese
> and Japanese.
I had the misconception of each Chinese character meaning a word until I
read "The
On 09/21/2018 04:18 PM, Adam D. Ruppe wrote:
> Well, for example, with a Chinese company, they may very well find
> forced English identifiers to be an annoyance.
Fully aggreed but as far as I know, Turkish companies use English in
source code.
Turkish alphabet is Latin based where dotted
On 23/09/18 04:29, sarn wrote:
On Sunday, 23 September 2018 at 00:18:06 UTC, Adam D. Ruppe wrote:
I have seen Japanese D code before on twitter, but cannot find it now
(surely because the search engines also share this bias).
You can find a lot more Japanese D code on this blogging platform:
On Sunday, 23 September 2018 at 00:18:06 UTC, Adam D. Ruppe wrote:
I have seen Japanese D code before on twitter, but cannot find
it now (surely because the search engines also share this bias).
You can find a lot more Japanese D code on this blogging platform:
https://qiita.com/tags/dlang
On Saturday, 22 September 2018 at 12:37:09 UTC, Steven
Schveighoffer wrote:
But aren't some (many?) Chinese/Japanese characters
representing whole words?
-Steve
Kind of hair-splitting, but it's more accurate to say that some
Chinese/Japanese words can be written with one character. Like
On Saturday, September 22, 2018 10:07:38 AM MDT Neia Neutuladh via
Digitalmars-d wrote:
> On Saturday, 22 September 2018 at 08:52:32 UTC, Jonathan M Davis
>
> wrote:
> > Unicode identifiers may make sense in a code base that is going
> > to be used solely by a group of developers who speak a
> >
On Saturday, 22 September 2018 at 19:59:42 UTC, Erik van Velzen
wrote:
Nobody in this thread so far has said they are programming in
non-ASCII.
This is the obvious observation bias I alluded to before: of
course people who don't read and write English aren't in this
thread, since they cannot
On Saturday, 22 September 2018 at 19:59:42 UTC, Erik van Velzen
wrote:
Nobody in this thread so far has said they are programming in
non-ASCII.
I did. https://git.ikeran.org/dhasenan/muzikilo
On Saturday, 22 September 2018 at 16:56:10 UTC, Neia Neutuladh
wrote:
On Saturday, 22 September 2018 at 16:56:10 UTC, Neia Neutuladh
wrote:
Walter was doing that thing that people in the US who only
speak English tend to do: forgetting that other people speak
other languages, and that people
On Saturday, 22 September 2018 at 12:35:27 UTC, Steven
Schveighoffer wrote:
But aren't we arguing about the wrong thing here? D already
accepts non-ASCII identifiers.
Walter was doing that thing that people in the US who only speak
English tend to do: forgetting that other people speak other
On Saturday, 22 September 2018 at 12:24:49 UTC, Shachar Shemesh
wrote:
If memory serves me right, hieroglyphs actually represent
consonants (vowels are implicit), and as such, are most
definitely "characters".
Egyptian hieroglyphics uses logographs (symbols representing
whole words, which
On Saturday, 22 September 2018 at 08:52:32 UTC, Jonathan M Davis
wrote:
Unicode identifiers may make sense in a code base that is going
to be used solely by a group of developers who speak a
particular language that uses a number a of non-ASCII
characters (especially languages like Chinese or
On Saturday, September 22, 2018 6:37:09 AM MDT Steven Schveighoffer via
Digitalmars-d wrote:
> On 9/22/18 4:52 AM, Jonathan M Davis wrote:
> >> I was laughing out loud when reading about composing "family"
> >> emojis with zero-width joiners. If you told me that was a tech
> >> parody, I'd have
On 9/22/18 4:52 AM, Jonathan M Davis wrote:
I was laughing out loud when reading about composing "family"
emojis with zero-width joiners. If you told me that was a tech
parody, I'd have believed it.
Honestly, I was horrified to find out that emojis were even in Unicode. It
makes no sense
On 9/21/18 9:08 PM, Neia Neutuladh wrote:
On Friday, 21 September 2018 at 20:25:54 UTC, Walter Bright wrote:
But identifiers? I haven't seen hardly any use of non-ascii
identifiers in C, C++, or D. In fact, I've seen zero use of it outside
of test cases. I don't see much point in expanding the
On 22/09/18 15:13, Thomas Mader wrote:
Would you suggest to remove such writing systems out of Unicode?
What should a museum do which is in need of a software to somehow manage
Egyptian hieroglyphs?
If memory serves me right, hieroglyphs actually represent consonants
(vowels are implicit),
On Saturday, 22 September 2018 at 11:28:48 UTC, Jonathan M Davis
wrote:
Unicode is supposed to be a universal way of representing every
character in every language. Emojis are not characters. They
are sequences of characters that people use to represent
images. I do not understand how an
On 22/09/18 14:28, Jonathan M Davis wrote:
As I said, it's exactly the same
as arguing that words should be represented in Unicode. Unfortunately,
however, at least some of them are in there. :|
- Jonathan M Davis
To be fair to them, that word is part of the "Arabic-representation
forms"
On Saturday, September 22, 2018 4:51:47 AM MDT Thomas Mader via Digitalmars-
d wrote:
> On Saturday, 22 September 2018 at 10:24:48 UTC, Shachar Shemesh
>
> wrote:
> > Thank Allah that someone said it before I had to. I could not
> > agree more. Encoding whole words as single Unicode code points
>
On Saturday, 22 September 2018 at 10:24:48 UTC, Shachar Shemesh
wrote:
Thank Allah that someone said it before I had to. I could not
agree more. Encoding whole words as single Unicode code points
makes no sense.
The goal of Unicode is to support diversity, if you argue against
that you don't
On 22/09/18 11:52, Jonathan M Davis wrote:
Honestly, I was horrified to find out that emojis were even in Unicode. It
makes no sense whatsover. Emojis are supposed to be sequences of characters
that can be interepreted as images. Treating them like Unicode symbols is
like treating entire words
On Saturday, 22 September 2018 at 01:08:26 UTC, Neia Neutuladh
wrote:
...you *do* know that not every codebase has people working on
it who only know English, right?
This topic boils down to diversity vs. productivity.
If supporting diversity in this case is questionable.
I work in a German
On Friday, September 21, 2018 10:54:59 PM MDT Joakim via Digitalmars-d
wrote:
> I'm torn. I completely agree with Adam and others that people
> should be able to use any language they want. But the Unicode
> spec is such a tire fire that I'm leery of extending support for
> it.
Unicode
On Saturday, 22 September 2018 at 04:54:59 UTC, Joakim wrote:
To wit, Windows linker error with Unicode symbol:
https://github.com/ldc-developers/ldc/pull/2850#issuecomment-422968161
That's a good argument for sticking to ASCII for name mangling.
I'm torn. I completely agree with Adam and
On Friday, 21 September 2018 at 20:25:54 UTC, Walter Bright wrote:
When I originally started with D, I thought non-ASCII
identifiers with Unicode was a good idea. I've since slowly
become less and less enthusiastic about it.
First off, D source text simply must (and does) fully support
On 22/09/2018 11:17 AM, Seb wrote:
In all seriousness I hate it when someone thought its funny to use the
lambda symbol as an identifier and I have to copy that symbol whenever I
want to use it because there's no convenient way to type it.
(This is already supported in D.)
This can be
On Friday, 21 September 2018 at 20:25:54 UTC, Walter Bright wrote:
But identifiers? I haven't seen hardly any use of non-ascii
identifiers in C, C++, or D. In fact, I've seen zero use of it
outside of test cases. I don't see much point in expanding the
support of it. If people use such
On Friday, 21 September 2018 at 23:17:42 UTC, Seb wrote:
A: Wait. Using emojis as identifiers is not a good idea?
B: Yes.
A: But the cool kids are doing it:
The C11 spec says that emoji should be allowed in identifiers
(ISO publication N1570 page 504/522), so it's not just the cool
kids.
On Friday, 21 September 2018 at 20:25:54 UTC, Walter Bright wrote:
But identifiers? I haven't seen hardly any use of non-ascii
identifiers in C, C++, or D. In fact, I've seen zero use of it
outside of test cases.
Do you look at Japanese D code much? Or Turkish? Or Chinese?
I know there are
On Friday, 21 September 2018 at 23:00:45 UTC, Erik van Velzen
wrote:
Agreed with Walter.
I'm all on board with i18n but I see no need for non-ascii
identifiers.
Even identifiers with a non-latin origin are usually written in
the latin script.
As for real-world usage I've seen Cyrillic
Agreed with Walter.
I'm all on board with i18n but I see no need for non-ascii
identifiers.
Even identifiers with a non-latin origin are usually written in
the latin script.
As for real-world usage I've seen Cyrillic identifiers a few
times in PHP.
When I originally started with D, I thought non-ASCII identifiers with Unicode
was a good idea. I've since slowly become less and less enthusiastic about it.
First off, D source text simply must (and does) fully support Unicode in
comments, characters, and string literals. That's not an issue.
94 matches
Mail list logo
