Hello, On 6/26/07, logan <[EMAIL PROTECTED]> wrote: > Offtopic: Sorry if it seems very obvious to you all, but I'm confused as to > why sipXtapi doesn't use STL over UtlString, UtlList, etc :-/?
Yeah, I've asked exactly same question about a year ago. So, you're not alone. :) Problem with STL raise when you try to build something for embedded target. sipXtapi is designed to work in embedded systems, so it could not use STL or, speaking more generic, C++ templates. Some problems with STL/templates: 1) They generate too much code. On embedded systems code size is very important thing. 2) STL is simply not supported on some platforms (e.g. some versions of WinCE), so you have to use third-party STL implementations, which, again increase code size. 3) They are not well-supported by some compilers. They generate too bloated code for it or just do not support them at all. 4) They rely on new/delete heavily. On embedded systems new/delete may be *very* slow, so we should have control over it. There may more reasons. This ones are most major over all, I think. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
