Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connectionsPath: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: James Kuyper Newsgroups: comp.lang.c Subject: Re: Baby X is bor nagain Date: Mon, 17 Jun 2024 19:52:16 -0400 Organization: A noiseless patient Spider Lines: 17 Message-ID: References: <20240613002933.000075c5@yahoo.com> <20240613174354.00005498@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Injection-Date: Tue, 18 Jun 2024 01:52:17 +0200 (CEST) Injection-Info: dont-email.me; posting-host="24730d7a2aace3b15633a7cca7d6ca34"; logging-data="1040351"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18BItZiKiG2GTQWz7Ge8kBIWVsPzF0g7hM=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:BnCvYq1IHbecOMzL8ivDHrFz4aY= Content-Language: en-US In-Reply-To: Bytes: 2464 On 6/17/24 12:21, David Brown wrote: .... > Having a distinction in optimisation between "debug" and "release" > builds is simply /wrong/. Release what you have debugged, debug what > you intend to release. I fully agree that you should debug what you intend to release; but I can't agree that it always makes sense to release what you've debugged. There are ways to debug code that make it horribly inefficient - they are also good ways to uncover certain kinds of bugs. There should be a debug mode where you enable that inefficient code, and track down and remove any bugs that you find. Then you go to release mode, and test it as thoroughly as possible with the code as it is intended to be released, which is never as much can be possible in debug mode. Do not release until the final version of the code has passed both sets of tests. If release testing uncovers a bug that requires a code change, that means that debug testing also needs to be redone.