News for hackers. Stuff that matters.

A comment on The Power of 10: Rules for Developing Safety-Critical Code [pdf]. Parent comment

Re:The Power of 10: Rules for Developing Safety-Critical Cod... by tgv on Wednesday June 28, 2023 @12:59PM (#36509256)
I don't think it's about that. Technically, everything is finite. But placing limits on the loops and restricting memory allocation bounds the complexity. It probably limits everything to P-time.
[ Parent | on HN ]
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by c_crank on Wednesday June 28, 2023 @01:13PM (#36509437)
Bounding the complexity is desirable for a system that should never fail due to software errors.
[ Parent | on HN ]
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by adrianN on Wednesday June 28, 2023 @02:04PM (#36510235)
You can easily have bounded loops and superexponential runtime.
[ Parent | on HN ]
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by tgv on Wednesday June 28, 2023 @04:15PM (#36511957)
Without dynamic memory allocation? I think you'd need at least O(n) memory to store enough state to go exponential. But it's some time I did complexity theory; I could be wrong.
[ Parent | on HN ]
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by adrianN on Thursday June 29, 2023 @12:53AM (#36516442)
Unless your input is read-only you should always have O(n) memory available.
[ Parent | on HN ]
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by l33t233372 on Wednesday June 28, 2023 @02:36PM (#36510624)
When everything is finite and memory is always limited, what are you meaningfully saying about the possible behaviors of software here?
[ Parent | on HN ]