I think my personal bugbear is the thing called Symbian C++. Its something like C++ with a bunch of macros and conventions. I must state I like C++!<br />So what is my problem with it?<br />- documentation: sometimes it is just not there. It is generated from the source, but at a couple of places only the function names are present, without any comment - cute....<br />- macros: as it is a descendant of Epoc, it has many archaic things: no try-catch (at least until 9.1), but a "nice" feature called clean-up stack: it is a semi-automatic garbage collection thing, but that should be done by a compiler, not by a programmer.<br />- no multiple inheritance (like Java) so extensive use of interfaces are required sometimes.<br />- all applications are dlls: no static data is allowed - and the compiler won't help much to pinpoint where you put in one (actually an ancient Epoc faq does give a good method)<br />...<br />I used a couple of Series 60 SDK from Nokia, so from now on its only for that:<br />- with Visual Studio as an IDE, it needed: Java SDK, J#, Perl installed just to install - nice system integration <img src="http://static.dreamincode.net/forums/style_emoticons/default/smile.gif" style="vertical-align:middle" emoid="
" border="0" alt="smile.gif" /><br />- the emulator implements the APIs of the OS, not emulates the hardware, it is not able to emulate timing/performance at all<br />- the compiler doesn't check bit alignment, so an app running nicely on the emu can produce very misterious crashes on production hardware (ARM processors have very strict restrictions on bit alignment, unlike x86)<br />- emulator in a release (not beta) was buggy, and all delete operators in the application caused an exception - not even bundled examples worked (really nice job Nokia)<br />- some examples contain bad practice, like the use of clean-up stack - actually the lack of...<br />- finally: some examples didn't even compile from the SDK, some crashed , some did not produce the expected result - ok, a lot actually worked.<br /><br />I am studying Symbian for my MSc, its really fun <img src="http://static.dreamincode.net/forums/style_emoticons/default/smile.gif" style="vertical-align:middle" emoid="" border="0" alt="smile.gif" /><br />Its not impossible, but it needs patience and intuitions...
</div>
" border="0" alt="smile.gif" /><br />- the emulator implements the APIs of the OS, not emulates the hardware, it is not able to emulate timing/performance at all<br />- the compiler doesn't check bit alignment, so an app running nicely on the emu can produce very misterious crashes on production hardware (ARM processors have very strict restrictions on bit alignment, unlike x86)<br />- emulator in a release (not beta) was buggy, and all delete operators in the application caused an exception - not even bundled examples worked (really nice job Nokia)<br />- some examples contain bad practice, like the use of clean-up stack - actually the lack of...<br />- finally: some examples didn't even compile from the SDK, some crashed , some did not produce the expected result - ok, a lot actually worked.<br /><br />I am studying Symbian for my MSc, its really fun <img src="http://static.dreamincode.net/forums/style_emoticons/default/smile.gif" style="vertical-align:middle" emoid="" border="0" alt="smile.gif" /><br />Its not impossible, but it needs patience and intuitions...</div>