Symbian OS design faults

Another guy who pretends to know how to make a software.
The only things rigth with his critic his the lacks of documentation in symbian.

Stl : an ineffective way to code. Several methods with different name do exactly the same, and other are non explicit. (seriously, who can make the diffence between string.size(), and string.length()).
At the contrary, Descriptor can be used for raw data. You don't have to care, if you deal with package send via ip, a picture from your build-in camera, of a japanese SMS.
It's the same!

The uge amont of classes! Yes. It's seem that this guy never seen an os before. Seriously, what does he think? the more fonctionnality you need, the more classes you have!

The exception mecanism.
With the RTTI, one of the worst idea of C++. Unlike in java, Exception In C++ is a very, very bad way to handle problem :
It never give your memory back.
It start a new thread, wich is much more expensive than in java.
eventually, if the method throw an error, you have no obligation to handle it. As a result, contrary to a java exception, a C++ exception is useless most of the time!!!

The compiler problem....
In fact, he could be rigth. Most of the time, on a different architecture (PC for example), it's correct. Except that this time, we are dealing with an os with huge problem of memory management, and binary compatibility...
Symbian works on new tools which build source code pattern for the devellopper. But nothing replace the brain.

TANY is the best thing on earth!
At last, you know if you expect any kind of data, or if you expect a function pointer to a void method!
It's so good, that I wish that other languages had this distinction!

Well, new Symbian OS versions will use the standard C++ exception handling .

Hi tote,
From where do u get this Information ?

Regards,
MeenuJ

That's true, and pretty good for porting.
But you can still use the symbian way for exceptions.