they make it cumbersome to use by hand, but not impossible
Such genius. It anticipates and neatly summarizes the problems I've had maintaining and supporting code written using reactive programming design patterns by a good 40 years.
But not too polite. The compiler wouldn't like that.
They seem similar to goto to me. With goto, the trigger specifies what to do. That's what command and commandfor do.
With comefrom, what to do specifies the trigger. That seems similar to the existing document.addEventListener() in Javascript.
with its grammar feature, it well might, or might as well.
TeX will also allow you to embed and force fonts.
Final step: Use something like Lyx, that will let you write and see the embedded font.
intro:
you are talking to an Indian who lives in India, and who knows Hindi (a language derived from Sanskrit) fluently (and has been complimented multiple times for his Hindi speaking ability by native Hindi speakers), and who has studied Sanskrit for 3 years in high school and then 2 years in college, and Hindi for 4 years in high school, including grammar, vocabulary and literature (both poetry and prose) in both languages), and also essay-writing in Hindi. and got a high score in class in both those languages, over all the years that he studied them.
and who has spoken Hindi for much of his adult life.
both those languages are written in Devanagari.
>Sanskrit is written in Devanagari script which is used by nearly a billion people, so any language that groks Unicode identifiers should handle it fine.
whether the (programming) language can grok Unicode, has nothing to do with the number of people who use either Sanskrit or Devanagari, so your statement lacks logic, overall.
you said:
>Sanskrit is written in Devanagari script which is used by nearly a billion people
that statement shows ignorance of actual facts.
here is why:
I had an idea about these points informally, already, being an Indian who lives in India, but I still did a few quick googles, to verify:
List of languages by number of native speakers in India:
https://en.m.wikipedia.org/wiki/List_of_languages_by_number_...
Demographics of India:
https://en.m.wikipedia.org/wiki/Demographics_of_India
https://www.google.com/search?q=number+of+people+who+use+dev...
top paragraph of the results of the above search:
>Today, the Devanagari script is used to write three major languages: Hindi (over 520 million speakers), Marathi (over 83 million speakers) and Nepali (over 14 million speakers).
even if you add the number of people in the Indian diaspora, such as in Fiji, the Caribbean, etc., you will not come to nearly a billion.
you made a wrong assumption:
> You want to pose a challenge, maybe try something like Rongorongo or Klingon.
you assumed that I was posing a challenge. I was not.
you seem to have not recognised that my comment was made in jest:
>b-b-but ... does Perl support Sanskrit?
first of all, I am posting again one of my earlier comments in reply to you:
https://news.ycombinator.com/user?id=fuzztester
let the whole world see it, and know you for the kind of guy you are, chuckadams, you creep, fake, ignoramus and liar.
acting (faux) scholarly and trying to tell me things (which are totally wrong) about my own country and culture, you jackass. you are laughable.
fool. everyone here noticed that you "cleverly" avoided replying to any of my above points, and instead tried to divert the topic by trying to insult me, you fuckhead and fucktard:
>I don't think you're capable of jest. Get some therapy.
hee hee hee.
not just me, no sane or decent person is interested in the opinions of a retard like you, except other retards like you, of which I know there are many, so some are sure to downvote my comment, but who the bloody fuck cares for votes or opinions of others, except losers like you and your friends, who I am sure you will encourage to waste their unvaluable time in downvoting, because laid off and no work and little money left, right? There are tons of recent posts on HN about all the people feeling the pain of no jobs and no money, which situation is partly if not largely due to the brain-dead shenanigans of jokers like you, who kept on demanding unsustainable raises, for years (which is why your jobs went to India and Ukraine and Mexico and ...), and job hopping for the same, which has now finally ended in so many of you guys being kicked out of your comfy, highly overpaid jobs, so that now you are on the street, scrabbling to make ends meet.
you are not capable of anything good, only of rotten shit! :)
I am fine. You need much more than therapy. you need a life, and to have interest in it. until then you will be as unhappy as you are now.
now, fuck off, you pathetic excuse for a human being.
don't waste your time insulting others gratuitously.
:) Google the double meaning (1 and 2) of that last word, or if you are unable to do it, swallow this crumb, dog:
https://www.dictionary.com/browse/gratuitously
and I don't give a flying shit if I am banned for this comment, because you started it, with your 2 ugly comments above, and because who gives a shit about hn in the real world anyway. let the whole world know how discriminatory HN is, with a very western-favoring slant, if not outright racism, towards Indians, Asians, etc., by comment posters, voters and moderators.
i'll repeat what i have quoted here a few times before; it's by Amy Hoy:
Fuck HN.
that is what she famously said, somewhere on one of her sites, some years ago. yes, so that means the rottenness of the site started or already existed back then, not just now.
so don't worry, you are in bad company.But still, so long as it’s a script in Unicode, it should all work fine.
Of course, COMEFROM's grown up (and very real) sibling is ALTER GOTO in COBOL.
https://www.cs.virginia.edu/~asb/teaching/cs415-fall05/docs/...
- A declarative mechanism to relate one element to another
- With a range of semantics for declaring interactivity invoked through their relationship
- At a high level, with explicit guarantees of consistent accessibility and UX
In a lot of ways, this looks a lot like what people describe when they wish for more HTML and less JS. (Except for the extreme-minimalist version of that which rejects web interactivity altogether.)
Let's bring back pronominal adverbs! You may already be familiar with such classics as "therefore" or "whereas". Why not revive all of them? No longer are "hereunder" and "thereinafter" the sole domain of lawyers. That alone would be an epic meme indeed, but we must go therebeyond. It is difficult to believe that anyone ever actually used words like "therethroughout" or "wherewithin", but we can make sure someone does.
You can even make up your own!
Just take any demonstrative (this/that/these/those), interrogative (what/which/who/where), or third-person personal pronoun, and turn it into the corresponding locative adverb, depending on whether you want to indicate being at, coming from, or going to something:
This -> Here/Hence/Hither;
That -> There/Thence/Thither;
What/who/which -> Where/Whence/Whither;
Him/Her/Them -> There/Thence/Thither; etc.
Makes sense? No questions? Great!
Now pick your favorite preposition and stick it on the end. Don't forget to experiment with some archaic prepositions like "anighst", "overthwart", and -- here's a really good one -- "withinside". That one means "within / inside" and I'm sure you can already see the potential.
"What place should I go into?" Nope! "Whitherwithinside should I go?" Now we're talking.
wowza, oops, i mean, wow, sir.
you inspired me to respire more deeply.
from which comes an irreversible desire to learn, deeply, about deep learning.
for (let i = 1; i <= 4; i++) {
woman.getOn(floor);
try {
getDown();
} catch (e) {
if (e instanceof NotUpError) {
getUp();
getDown();
}
}
}goto and comefrom
with optional synonyms:
leave to and return from
the above can be shortened to as little as two letters each:
go and co
le and re
for fans of succinctness / conciseness.
PRs are open.
Leave I follow, but doesn't "return from" rightly describe a continuation as opposed to "come from" which is a nonlocal goto?
They are perplexing until they aren't. Model stack frames as independent state. When you return from a function the stack frame can stick around. Now later, place your stack pointer back in the frame that you returned from earlier.
Add a convention for passing arguments when you update the stack pointer as above. Now you have continuations.
Of course modern LLVM already breaks it up into chunks anyway (given certain flags at least) so it likely isn't contiguous regardless.