321–330 of 412 posts
Earlier quoted context omitted.
The joke really only works if you use his first name! The complete joke is that "by value" means pronouncing first and last name to sound like "Nickles Worth".
The way I understand it, it doesn't -- by name (aka by reference) vs by value, as in function arguments.
Earlier quoted context omitted.
> Is there even a maintained Pascal compiler anymore? Of course https://www.freepascal.org/
Nice. Although "latest news" are from 2021.
Earlier quoted context omitted.
I saw it stated as pronounced as Veert, somewhere, maybe in his Wikipedia or Wikiquote pages.
It's pronounced with an ɪ like in "wit".
Earlier quoted context omitted.
Modula2 was available and got used on Amiga. Silly teenager me found such high level languages "cheating" at the time.
Lords of the Rising Sun was written in Modula2 on the Amiga https://www.google.com/search?q=lords+of+the+rising+sun My understanding (please correct me) is that Turbo Pascal on PC was actually Modula2 ?
After having read some of the comments on Pascal here -- fellow HNers, what's your view on Pascal as a teaching/introductory language in 2023, for children aged 10+? Mostly thinking of FreePascal, but TurboPascal in DOSBox/FreeDOS/SvarDOS is also a possibility. I'm also thankful for references to "timeless" Pascal books or online teaching materials that would be accessible for a 10+ year old kid who is fine with read…
I would rather pick Python or Kotlin.
Pascal was my second language, after BASIC. I was about twelve and pointers cost me a little to understand. But the first hurdle was not having line numbers. It seemed weird. In the end, it was definitely worth the effort, and I learnt good habits from it. I used it in college, and I suppose I kinda still do, because I do a lot of PL/SQL. He was hugely important for generations of coders. RIP.
Earlier quoted context omitted.
It's pronounced with an ɪ like in "wit".
Okay, either me or the ref. may have been wrong. but I distinctly remember "Veert", because it was non-intuitive to me (as the way to pronounce Wirth), as a guy who didn't know any German at the time, only English. So the ref., probably.
Earlier quoted context omitted.
Sort of and sort of not. The key thing about 2023-era asynchronous versus 1995-era cooperative multitasking is code readability and conciseness. Under the hood, I'm expressing the same thing, but Windows 3.1 code was not fun to write. Python / JavaScript, once you wrap your head around it, is. The new semantics are very readable, and rapidly improving too. The old ones were impossible to make readable. You could argu…
Exactly. The way I think about it, the "async" keyword transforms function code so that local variables are no longer bound to the stack, making it possible to pause function execution (using "await") and resume it at an arbitrary time. Performing that transformation manually is a fair amount of work and it's prone to errors, but that's what we did when we wrote cooperatively multitasked code.
That's my point, we still do that. And based on your phrasing we're forgetting it :)
Earlier quoted context omitted.
It's pronounced with an ɪ like in "wit".
I think that the "i" sound like in "wit" does not exist in German. The Germans pronounce "i" like English speakers pronounce "ee".
Earlier quoted context omitted.
It's pronounced with an ɪ like in "wit".
Okay, either me or the ref. may have been wrong. but I distinctly remember "Veert", because it was non-intuitive to me (as the way to pronounce Wirth), as a guy who didn't know any German at the time, only English. So the ref., probably.
"Wit" is just wrong. Perhaps that was a joke that I missed about the man's humour.