Earlier quoted context omitted.
Tied with Coq for best name
[flagged]
confused why coc is okay, dong is not okay.
Python’s Preprocessor
31–40 of 109 posts
Re: Python’s Preprocessor
#32Re: Python’s Preprocessor
#33Now that I know this is possible, it seems like it would be a fun addition to the Hy, Hissp, and Coconut projects: https://hylang.org/ https://github.com/gilch/hissp http://coconut-lang.org/
Re: Python’s Preprocessor
#34>>> from __future__ import braces File " ", line 1 SyntaxError: not a chance For those interested in how this (hilarious) error text came to be, it's been hardcoded in cpython since 2001! https://github.com/python/cpython/commit/ad3d3f2f3f19833f59f... The author, Jeremy Hylton, is now a Principal Engineer at Google working on AI search quality. It's quite remarkable that in 24 years, a single person's career has gone…
Reminds me of `break rust;` causing the Rust compiler to emit an internal compiler error. I wonder which other languages have similar easter eggs.
Re: Python’s Preprocessor
#35Part of me says that python has not gone out of its way to expose preprocessor hooks for good reason, and reasonable adults should stay away from it. The other part wants nothing to do with reasonable adults anyhow. Such fun could be had.
Python has a whole bit about how it is for "consenting adults" and that's why it lacks public/private visibility modifiers and presumably why it exposes all other manner of metaprogramming magic. If they were worried about "reasonable adults", these other design decisions would be curious. :)
Re: Python’s Preprocessor
#36Earlier quoted context omitted.
Dong is a very common name in some countries.
I think it's the name of Vietnam's currency.
Also a common name as is Phuc.
I had a partner that was a translation coordinator and they would play me this VM from one of the Vietnamese translators, every time he called he would say, “Hi this Phuc, ha ha that is funny to you, anyway …”
Re: Python’s Preprocessor
#37>>> from __future__ import braces File " ", line 1 SyntaxError: not a chance For those interested in how this (hilarious) error text came to be, it's been hardcoded in cpython since 2001! https://github.com/python/cpython/commit/ad3d3f2f3f19833f59f... The author, Jeremy Hylton, is now a Principal Engineer at Google working on AI search quality. It's quite remarkable that in 24 years, a single person's career has gone…
20 years at google, now thats some F-U money!
Re: Python’s Preprocessor
#38Earlier quoted context omitted.
Not python but literally yesterday I had do a double take when I saw https://github.com/janestreet/sexplib
I was introduced to S-Expressions a few decades ago yet it is still the case that 100% of the time I pronounce 'SEXP' as 'SEX-P'
I occasionally run across something called K8-Sexecutor, or at least that's how I pronounce it.
Re: Python’s Preprocessor
#39Earlier quoted context omitted.
Not python but literally yesterday I had do a double take when I saw https://github.com/janestreet/sexplib
I was introduced to S-Expressions a few decades ago yet it is still the case that 100% of the time I pronounce 'SEXP' as 'SEX-P'
Ah the traditional lispish naming for predicate functions, applied to questions of an amorous nature!