Optimize your workflow

#define A else
#define B break
#define C char
#define D double
#define E enum
#define F  float
#define G goto
#define H short
#define I int
#define J case
#define K const
#define L long
#define M continue
#define N  unsigned
#define O  for
#define P  volatile
#define Q if
#define R return 
#define S switch
#define T typedef
#define U union  
#define V void
#define W while
#define X signed 
#define Y struct
#define Z sizeof

since you will be constantly switch caps-lock or shift, it better to sacrifice one-letter variables(which are bad practice for readability anyway) and make all the identifiers lowercase. Despite the productivity boosts, you'll discover how error-prone this system is(i've tried it already) and abandon it for something more verbose(like u1-u8) but less prone to errors(and easily extensible).

http://dis.4chan.org/read/prog/1320683434/127

I did this ages ago. I should write some code with it.

F8 s[ZS];U4 p=0;V e(O U1*m){Fi(Xe,"%s\n",m);Ex(1);}V u(F8 x){I(p==ZS)e("stack"
" is too high!");s[p++]=x;}F8 o(V){I(!p)e("stack is empty!");R s[--p];}M{U4 i;
F8 x;F(i=1;i<c;++i){S(v[i][0]){C'\0':e("empty command line argument");B;C'0':C
'1':C'2':C'3':C'4':C'5':C'6':C'7':C'8':C'9':u(Af(v[i]));B;C'+':u(o()+o());B; C
'-':x=o();u(o()-x);B;C'*':u(o()*o());B;C'/':x=o();u(o()/x);B;A:e("unknown ope"
"rator");B;}}P("%g\n",o());R 0;}
Yeah.