It depends on what you mean by C++. Using classes and stream I/O isn't that expensive. When you start using templates, rtti, and STL and stuff your code grows in size and the library requirements grow. I'm doing a hybrid embedded project against 2.4 of the kernel. It's closer to a closed PC than a real embedded project though. Guennadi Liakhovetski wrote: > Hello > > Here's my next question: how generally bad is writing applications for > embedded systems in C++? Problems - compiling (cross-compiling?), > size? And in general - to what extent is it possible to write applications > for embedded systems? My understanding is that they are VERY > different... And what kernels are mainly used in ES's? 2.0.x, 2.2.x, > 2.4.x? > > Thanks > Guennadi -- To unsubscribe from this list, send a message to [EMAIL PROTECTED] with the command "unsubscribe linux-embedded" in the message body. For more information, see <http://waste.org/mail/linux-embedded>.
