Do you mean you want like C#?
public class 그뤼고
{
private 이 이 {get;set;}
public 그뤼고()
{
var 문좌열은 = 이.문좌열은;
var 기ㅖ버역을 = Enumerable.Range(0, 10);
var 오타비문이 = 기ㅖ버역을.Select(요 => 요);
}
}
public class 이
{
public int 문좌열은 {get;set;}
}
Re:C++ Modules Might Be Dead-On-Arrival
by lifthrasiir on Monday January 28, 2019 @06:34PM
(#19022202)
Sometimes, though my example was intentionally obscured to prevent machine translation and you were not aware of Korean conjugations (usually omitted in identifiers) ;-)
I have seen numerous instances of pseudo-English when it comes to naming. It is hard to name things in non-native tongues. When reasonable, reducing that overhead can be indeed beneficial.
Re:C++ Modules Might Be Dead-On-Arrival
by yarosv on Wednesday February 06, 2019 @11:18AM
(#19096400)
Oops (yes, I don't know what it meant).
I mean I speak Ukrainian and Russian. If I saw the code like that in my native tongue, I would be upset.
Plus it is pain to alt+shift between languages all the time.
Uh, no? You are not supposed to be able to read this valid Unicode string literal in Korean: `"그뤼고 이 문좌열은 일부려 기ㅖ버역을 어럽게하러고 오타비문이 산개해 있구먼요."`
Also a significant portion (and possibly the majority) of codes would be ever read and written by a small group of people, often sharing a common language other than English, so non-English code is just fine for them. If you are saying that a public library should be written in English, I almost agree---there would be some exceptions though.