Tamas Rudnai wrote:

> Exactly! I am reverse engineering software as primary job. [...] An OO
> written code is horrible sometimes - not impossible but takes time to
> fully analyse those. Similarly a multi threaded concurrent program is
> not so easy to get it throuh on the relations in between the threads the
> shared objects, the synchronization mechanishm etc. 

Well... easy reverse engineering is one of the "requirements" that's not on
my list of priorities when I'm writing code :)  Of course OO code (or any
form of C++ style virtual inheritance) with its frequent indirections must
be a real pain to reverse engineer; the procedural model is closer to the
actual machine language, so it probably is easier. But I don't care /at
all/ about this. 

> OO and multi threading / multi processing is for human, we could imagine
> our program easier like that.

Not sure what you mean, but the programs I write I actually write for
humans (both to use the compiled result and to understand the sources). So
anything that improves those two goals (usability and work to spec,
maintainability) moves up on my list of priorities.

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist