I would not use Perl. Nor any language that cannot be compiled to machine code and run from ROM. Harddisks can suffer dropouts.

In at least one machine code, a one-bit change in an opcode could change a common condition JUMP instruction in to a HALT instruction.

A single bit change in a ascii '0' makes it an ascii '1' and vice vera. In Perl, that could make 

while( 1 ) {
   ## Critical code
}

[download]

Into 

while( 0 ) {
    ## Critical code that never gets run.
}

[download]

With compiled code written to ROM (PROM, EEPROM maybe), preferably with EEC and an embedded crc check, testing can validate the final binary image. There are simply too many possibilities of accidental or malicious change to the source code of non-compiled, and runtime compiled languages.

I'd use Perl to prototype it maybe, and to test it, but not for final, life-critical application code.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Projects where people can die by BrowserUk
in thread Projects where people can die by cog

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.