Bad points:
1) Leaks
2) Inconsistent style
3) Really bizzare macros, etc.
Let's put one thing straigt: I merged it already in this early stage (I KNEW
it wasn't yet the way it should be, for example the macro thingy: It started
out as 2line-macro's, but went bigger. In the optimization and
I really dislike the way you are handling with this issue: first silently
agree,
I keep seeing this thrown around. 'Silent approval' is an interesting
concept. How do you distinguish it from 'silent disapproval'? Are you sure
you didn't make an assumption about the way people felt? (We
I *NEVER* have anything to say until I have seen the code. Otherwise,
it's just a bunch of castles in the air.
Okay, that's a point. That is not the custom where I learnwork, actually,
there is a saying that design planning is 67% of the job, implementing
just 33%. That is if you want a good
Maybe you don't understand my way of coding (emphasis on CORRECTNESS, the
rest comes in later stages). In fact I was REALLY in fast-coding mode
because I wanted to commit/merge it before the big part of that introduction
I was co-organising. I thought you would be able to discuss it, so after
