Related articles |
---|
Parser Generators for Multiple Protocols in an Embedded Device nou.dadoun@polycom.com (2002-04-23) |
Re: Parser Generators for Multiple Protocols in an Embedded Device dr_feriozi@prodigy.net (SLK Parsers) (2002-04-24) |
Re: Parser Generators for Multiple Protocols in an Embedded Device k.prasad@attbi.com (Kamal R. Prasad) (2002-04-29) |
Re: Parser Generators for Multiple Protocols in an Embedded Device haberg@matematik.su.se (2002-05-01) |
Re: Parser Generators for Multiple Protocols in an Embedded Device joachim.durchholz@munich.netsurf.de (Joachim Durchholz) (2002-05-03) |
Re: Parser Generators for Multiple Protocols in an Embedded Device haberg@matematik.su.se (2002-05-04) |
Re: Parser Generators for Multiple Protocols in an Embedded Device k.prasad@attbi.com (Kamal R. Prasad) (2002-05-04) |
From: | "Kamal R. Prasad" <k.prasad@attbi.com> |
Newsgroups: | comp.compilers,comp.lang.misc |
Date: | 4 May 2002 21:14:23 -0400 |
Organization: | AT&T Broadband |
References: | 02-04-133 02-04-154 02-05-006 02-05-019 |
Keywords: | design |
Posted-Date: | 04 May 2002 21:14:23 EDT |
That is correct. an embedded device is by definition a device with
scarce resources. most embedded (micro-)kernels reduce the footprint
by removing standard features from the OS. as regards smaller object
code from C++ -good for you if it works. OS developers code critical
stuff in assembly instead of C to improve performance. eg:-
__syscall() which does context switch in Unix is usally implemented in
assembly. The folks at Javasoft gave up on using Java to create a
JavaOS (and Java has a smaller object code because it does not have
standard C featires unlike C++). so, IMHO it is quite daunting to
write the embedded OS (or parts of it) in C++.
regards -kamal
"Joachim Durchholz" <joachim.durchholz@munich.netsurf.de> wrote in message
> Hans Aberg wrote:
> > It means that also embedded programming, as memory becomes plenty,
> > will make use of high level programming techniques.
>
> Memory in embedded devices has never been plenty, and I doubt it ever will.
>
> There are two limiting factors: component price and power consumption.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.