Deutsch English Français Italiano |
<vba56o$3te58$3@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Thomas Koenig <tkoenig@netcologne.de> Newsgroups: comp.arch Subject: Re: Computer architects leaving Intel... Date: Wed, 4 Sep 2024 17:25:44 -0000 (UTC) Organization: A noiseless patient Spider Lines: 19 Message-ID: <vba56o$3te58$3@dont-email.me> References: <2024Aug30.161204@mips.complang.tuwien.ac.at> <memo.20240830164247.19028y@jgd.cix.co.uk> <vasruo$id3b$1@dont-email.me> <2024Aug30.195831@mips.complang.tuwien.ac.at> <vat5ap$jthk$2@dont-email.me> <vaunhb$vckc$1@dont-email.me> <vautmu$vr5r$1@dont-email.me> <2024Aug31.170347@mips.complang.tuwien.ac.at> <vavpnh$13tj0$2@dont-email.me> <vb00c2$150ia$1@dont-email.me> <505954890d8461c1f4082b1beecd453c@www.novabbs.org> <vb0kh2$12ukk$1@dont-email.me> <vb3smg$1ta6s$1@dont-email.me> <vb4q5o$12ukk$3@dont-email.me> <vb6a16$38aj5$1@dont-email.me> <vb7evj$12ukk$4@dont-email.me> <vb8587$3gq7e$1@dont-email.me> <vb91e7$3o797$1@dont-email.me> <vb9eeh$3q993$1@dont-email.me> Injection-Date: Wed, 04 Sep 2024 19:25:45 +0200 (CEST) Injection-Info: dont-email.me; posting-host="04b9462bf8233c0522365da918e60878"; logging-data="4110504"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/+oVilOTwkWSTu8vphDJucgCHQIIObyro=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:oDGYneVvzzZ/OHRN4NO7e/0Kc3Y= Bytes: 2429 David Brown <david.brown@hesbynett.no> schrieb: > I'm all in favour of temporarily having checks for overflow (and other > errors) during debugging, but I am sceptical to having distinct > debug/release builds. It encourages people to use debug builds during > development, bug hunting and testing, then when all looks good they > switch to release build and deploy it. I prefer a single build, and > enable run-time checks on parts of it if and when necessary. Wise man once said... # It is absurd to make elaborate security checks on debugging runs, # when no trust is put in the results, and then remove them in # production runs, when an erroneous result could be expensive or # disastrous. What would we think of a sailing enthusiast who wears # his lifejacket when training on dry land, but takes it off as soon # as he goes to sea? (C.A.R. Hoare, in "Hints on Programming Language Desin)