> I don't know, but I would guess that embedded coding standards may be > "liberalizing" (for lack of a better word) in response to hardware > changes. Actual CPUs, with hardware support for a stack are the norm > these day, no? Don't only very high volume, low cost mass market > products (e.g. remote controls) still use PIC controllers?
Well, there's "embedded" as in "runs windows mobile" and then there's "embedded" as in "must acheive a frame rate of 30 hz". Hardware improvements cannot guarantee frame rate if the system architecture cannot guarantee every step is a fixed operation. i.e. any system that will stop and read a file of undefined length until EOF is reached is the first kind of embedded, a small "desktop". if you're working on the "must achieve a frame rate of 30 hz" kind of device, then you're system architecture is going to be fundamentally different than desktop applications. It's an entirely different mindset. _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
