an underrated part of knowing how to use a DAW is that if i ever hear a song and think "i wish they did this part a little differently", i can just, like, change it. like i can make my own personal version that's tweaked in small ways which sound better to me. not enough people do this i think. [...]
ok so i've been reading the "specification" from "the c programming language" (1st edition). alongside that, i've also been reading the c89 rationale document, and the source code for the 7th edition unix c compiler. i've also been reading some other related stuff.
and i didn't really know anything about pre-ansi c until i did this research, but i found a bunch of stuff, so i'm documenting my findings here :3 [...]
PEP 3099 "Things that will Not Change in Python 3000" begins with:
Some ideas are just bad. While some thoughts on Python evolution are constructive, some go against the basic tenets of Python so egregiously that it would be like asking someone to run in a circle: it gets you nowhere, even for Python 3000, where extraordinary proposals are allowed. [...]
If you think you should suggest any of the listed ideas it would be better to just step away from the computer, go outside, and enjoy yourself. Being active outdoors by napping in a nice patch of grass is more productive than bringing up a beating-a-dead-horse idea and having people tell you how dead the idea is.
looking through the list of ideas that will "never be added to python", three of them have since been added to python: [...]
Two function types with different language linkages are distinct types even if they are otherwise identical.the idea is that some implementations may have different calling conventions for c++ functions than for c functions, so they can't be intermixed [...]