Re:Comparing C and C++ usage and performance with a real wor...
by coldtea on Sunday September 03, 2017 @01:34PM
(#15162665)
Doesn't have to be hygienic, it's enough that fixing it doesn't justify the time/money costs for the programmer.
[ Parent
| on HN ]
Re:Comparing C and C++ usage and performance with a real wor...
by blub on Sunday September 03, 2017 @06:58PM
(#15164462)
We wouldn't want the programmer to spend too much money/time on fixing errors. After all, it's not like people would die if there's an error in the missile software: http://www.gao.gov/mobile/products/IMTEC-92-26
Not to mention they added even more HW to work around the leaks. No wonder those projects always run over budget.
Re:Comparing C and C++ usage and performance with a real wor...
by coldtea on Monday September 04, 2017 @04:08AM
(#15166540)
>We wouldn't want the programmer to spend too much money/time on fixing errors. After all, it's not like people would die if there's an error in the missile software
When exactly did pkg_config became missile software?
As they say in meme-land, "that escalated quickly".
Here's a novel idea: how about the appropriate level of effort/time/YAGNI-stuff based on the domain?
Or do you write one-time scripts with MISRA rules?
Re:Comparing C and C++ usage and performance with a real wor...
by blub on Monday September 04, 2017 @07:19AM
(#15167366)
The sub-thread I replied to was linking to an anecdote about missile software.
But I still think not freeing is pretty lame even in short-lived tools. If one is using a no-op deallocator at least the code is designed properly and could be repurposed.