[Interest] Chasing a standard
roland at logikalsolutions.com
roland at logikalsolutions.com
Mon Nov 5 16:54:36 CET 2018
Quoting Jason H <jhihn at gmx.com>:
>>
>> Very good catch.
>>
>> Battery powered embedded systems in the medical and industrial world
>> have wretched dynamic memory allocation. If the underlying
>> implementation does away with shallow/no-copy passing between threads
>> for some std:: version which requires giahugic (given 512 MEG total
>> working RAM) data sets with sluggish allocation (if enough memory
>> exists at all) this is an extreme price.
>
> Medical and Space-based systems should use the NASA (JPL) coding
> standard. Chief of which is no dynamic memory after initialization.
> So all your container arguments are moot.
> ( https://lars-lab.jpl.nasa.gov/JPL_Coding_Standard_C.pdf ) (Unless
> of course you're using mysmic memory after initialization in a
> medical device (But then, WHY!?))
>
I've never worked on a single medical device which utilized JPL. Not
one. Not saying there isn't one somewhere in the world, but, I've
never seen it. One could not use Qt in a medical device if strictly
adhering to JPL. Something simple like an error message to syslog
being built with a QString would violate such a standard. You couldn't
fill in the values with .arg().
No, the container issue in medical device world isn't moot. It's a
clear and present danger.
--
Roland Hughes, President
Logikal Solutions
(630) 205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us
More information about the Interest
mailing list