Python's Context Dependent Syntax Soup: 「… in …」 And 「… not in …」

, , …,

Python has these operators to check if a key exist in hash table or element exist in list:

note that ② is not necessary. It can simply be done with not (x in list).

Now, the not operator has multiple meanings, depending on context. It compounds on syntax complexity. Now, not in is actually a operator. Having English words acting as operator and not function is bad enough, but now that operator is 2 words, separated by space! So, syntactically, it becomes not distinguishable from statements, or the tens of idiosyncratic syntax of C such as its “for”, “while”.

note that the syntax … in … is similar to the form for … in …, and also the list comprehension syntax [… for … in …]. Each have completely different semantics. 〔☛ Computer Language Design: What's List Comprehension and Why is It Harmful?

this is the state of the affair of syntax soup. When you learn a language, there's little governing principle of what symbol can go where (as in formal language❕), instead, you learn by rote of what symbols or words can go where in what context means what.

but, the ‹k› in ‹d› is itself idiotic. Python has a has_key() method for dictionary, which is in sync with the 20 other methods on dict. Method syntax is systematic and also informative of its meaning because of the name. Though, strangely, python decided to deprecate it, and in python 3, it's gone.

〔☛ Python: Dictionary (Key/Value Pair, Hash)

comment at g+ discussion

Soup. Soup. It's All good Soup.

JavaScript Syntax Soup

JavaScript Syntax Soup: 「p in o」 vs 「for (p in o) {…}」

blog comments powered by Disqus