I propose a new, more threatening kind of control flow.
do {
/* something */
} or else {
/* you don't want to find out */
}
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
I propose a new, more threatening kind of control flow.
do {
/* something */
} or else {
/* you don't want to find out */
}
Some C++ style guides suggest the following naming convention for functions that crash on any error
OpenFileOrDie()
ifn't(!valid)
halp?
I believe that resolves the same as
ain't!(!untrue)
ain't (nothin)
{
put(a, "heartache")
tell(me, "why")
ain't(nothing)
{
put(a, "mistake")
//...
}
}
What's wrong with "else"
if(condition) {#block never used} else {#actually do a thing}
Vs
ifn't(condition) {#actually do a thing}
Vs
if!(condition) {#actually do a thing}
vs
if (not condition) {#actually do a thing}