Comp Lang: Bit Operators Idiocy
in low level programing languages such as C, there is a idiocy: bit operators on integers. e.g.
& | <<
They are confounding of concepts. What should happen, is to have a dedicated bits type.
Bit operator in programing languages is a low level phenomenon. It's a computer engineering side effect of low level language feature creeping up to high level languages.
other similar idiocy of C monkeys are bitmask used as function parameters.
〔see Comp Lang: Hack of Bitmask as Boolean Parameters〕
And also the idiocy of using logic operator as control flow. This still persist to this day as fashionable style.
〔see Comp Lang: Abuse of Logic Operators (Short-Circuit) as Control Flow〕
similar idiocy is language that does not have dedicated true/false values, but piggy back on integer 1, 0, empty string, empty list, etc.
a logical description of these problems is that, their computing model is sloppy, and or their computing model is skewed (not orthogonal).
the practical effect of these designs and practice is that, it creates confusion, complexity, unreadable, to all except the fan club boys of each.
Programing Language Design
- Ontology of Programing Languages
- Comp Lang: Why I Hate Exceptions
- Comp Lang: Iterator, Enumerator, Abstraction Went Wrong (2016)
- Comp Lang: Should Array Index Start at 0 or 1?
- Comp Lang: Where does the “main” function in programing languages came from?
- Comp Lang: is the Map Function Functional Programing in Syntax or Semantics
- Comp Lang: Should Map Function Specify Order
- Comp Lang: Abuse of Logic Operators (Short-Circuit) as Control Flow
- Comp Lang: Bit Operators Idiocy
- Comp Lang: Hack of Bitmask as Boolean Parameters
- Comp Lang: Function Dependency
- The Complexity of Java Access Specifiers
- Comp Lang: C Cpp Java Coders Don't Know Scientific Programing Languages