Post funny things about programming here! (Or just rant about your favourite programming language.)
Partially unrelated to the meme, but I find it almost malicious how some python keywords are named differently from the nearly universal counterpart of other languagues.
This/self, continue/pass, catch/except and they couldn't find a different word for switch so they just didn't implement it.
It's as if the original designers purposefully wanted to be different for the sake of it.
pass and continue are absolutely not equal (pass is a noop, and python has a continue keyword that does what you think), and switch is called match like in many other languages. except is weird though.
"except" is also used in Pascal (or at least the main derivatives of it), but not sure if that's older than its use in Python or not.
I read that self as a keyword also has quite a history. It was already used in Smalltalk, an OOP language from the early 80's.
Isn't self not actually a keyword? Like you can name the first variable in a class method anything and it will behave like self.
You could use "this" instead of "self". And if you want a lynch mob of Python programmers outside your house, make a push request with that to some commonly used package.
I think there will be a lynch mob of git users outside your house for calling PR as "push request".
I've been wondering about the noise.
Edit: turns out, they weren't there to lynch me. They just gave me a two hour lecture on proper usage of git.
only github users. git itself doesn't have PRs, and other forges call them different things. gitlab calls them merge requests, pico calls them patch requests...
Python does have a switch statement now, actually. And yes, they went out of their way to call it something different - match.
https://docs.python.org/3/tutorial/controlflow.html#match-statements
match isn't just equivalent to switch though, so in this case it actually makes sense to call it something different.
This is very true. Match statements are much more powerful that switch statements in any other language.
For instance:
PHP naming "::" a Paamayim Nekudotayim is also pretty infamous.
When I'm designing shit, I'm pretty zealous about borrowing terminology from anything even vaguely related to avoid this.
List and Array terminology also bothers me ... Why not just call it an array?
But python lists are not like the base arrays in other languages. They function more like List<> or vector (C++ had to be special) and are named appropriately.
In Python, self is not a keyword, it’s a conventional variable name. You can replace all instances of “self” with “this” and your code will work the same.
Lua might have been a better choice, since self is special in lua.
Kinda.
Lua defines it implicitly only when you use the
function foo:bar(a, b, c) -- note the colon
syntactic sugar, which gets translated to
function foo.bar(self, a, b, c) -- note the period
In all cases, self is a regular variable name. You can even redeclare a new local with that name even when the old one is in scope.
Edit: some typos
I don't see how what you said is inconsistent with me saying "self" is special in lua. Note that I did not say it's a keyword.
Derp, I misread.
Python is just distancing itself from JS.
TBF the last two bullet points are verbose descriptions of the thing it means in C++, Java, and Python too. It's just that in JS, "this" can also be used in other places.
But yeah, in practice, every time I write JS I want to throw my hands in the air and shout "this is bullshit", but never know what "this" refers to... :D
Yeah that's fair, though it also discusses that whole prototype thing that JS has going on
Sweet dreams are made of this
Rust: Borrow handler got mad at you for asking
(I'd assume)
It's either a reference to an object instance, or the instance itself (depending on whether you specified &mut self, &self or just self).
Don't forget Self, the type of self.
I was working on a C code base with classes, inheritance, and polymorphism, all done by hands and macros.
Something like
typedef struct s_some_class {
void (*method)(this *s_some_class);
} t_some_class;
Overall, learning C was the best enabler in my whole career. For instance I was learning Python by tinkering with CPython VM, so when I see these ‘WAT’ quircks I know exactly what’s up.
Interesting, how did they do inheritance? Something like void *super? Also why not switch to CPP if you wanna do OOP?
In general, 'classes' declarations were done with macro. I don't remember the exact code — something akin to
BEGIN_CLASS(A, Parent);
CLASS_MEMBER(a...)
END_CLASS();
The project had started before C++ existed, and the switch would be too costly. It's not just OOP part, also reflection mechanism with bindings to the homemade scripting language, and multi-platform UI library. It was a gem of its time.
That sounds like quite a challenge to maintain, to speak in euphemisms ;)
Revolutionary technologies of the '80 make me appreciate modern programming languages and especially tooling much more.
Alternative image for C: Mr. Incredible: "A PARAMETER IS A PARAMETER!"
My JS:
Ah, you mean that?
In Python you can use this as a variable name
In Python you can use 🍆 as a variable name.
Edit: oops, guess I was mistaken, you can use most Unicode but emojis are not valid.
Edit: oops, guess I was mistaken, you can use most Unicode but emojis are not valid.
That actually seems even more arbitrary. Like, do they just hate fun?
you might be thinking of Rust.