> reimplement it completely in order to make it run under another O/S. Large
> applications may live a long time and have to be maintained by people that
> haven't been involved in the initial implementation and design.
> Following colors that are in fashion is not the right way to deal with
> the long term. Each time you go in the wrong direction, you will pay it
> a lot.
Multithreading isn't a something that's in "fasion". It's a good technique
that most application programmers should learn and apply in normal programming
practice if it gives additional feature that would be there otherwise.
The other things is that multithreading with methodical synchronization
primitives like in Java make multithreading very easy. By simply making this
multithreading design approach methodical, you simple solve all the above
criteria you listed above *VERY* easily.
The comments you've made only apply to haphazard useage of standard C Posix
threading and not current OO kits.
Stuff like Java and the BeOS API in C++ make this kind of stuff very simple
for you and me a like. I recommend reexamining the current view that you
have on threading with modern OO kits.
bill
> Gérard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/