A lot of the stuff presented here is mainstream practice in Tcl (e.g., new constructs, dbg evaluation). Tcl is seriously underappreciated language.
In my programming whenever I see myself writing blubber (I like that word), I just factor it out into a separate procedure and give it a descriptive name.
So when I'm reading the code of the calling routine, I rarely see blubber; it's contained in simple routines that are easy to read/verify.
Most of the examples here amount to thoughtful library development. With a good library, C++ and macro processor can also many of these things.
Here's a version of aif that works for most cases (I'm not claiming that C has the expressive power of Lisp):
#define aif(expr, val, code...) \
{ if ((expr) != (val)) { \
code ; \
} \
}
IMHO, this is good enough for blubber reduction.