Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Janis Papanagnou Newsgroups: comp.lang.c Subject: Re: Which code style do you prefer the most? Date: Wed, 26 Feb 2025 13:25:53 +0100 Organization: A noiseless patient Spider Lines: 22 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Date: Wed, 26 Feb 2025 13:25:54 +0100 (CET) Injection-Info: dont-email.me; posting-host="4f0782fc39d9cc4b721840988cfbfa82"; logging-data="2699722"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18e4wNS1OzPaff3STxoQa5W" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Cancel-Lock: sha1:ItYBFHB2kLFlburZjrrwAz8Hu2c= In-Reply-To: Bytes: 2114 On 26.02.2025 09:41, David Brown wrote: > [...] > > Even then, however, I would suggest challenging the status quo. Definitely. > That > does not mean overriding the existing style choices, but it /does/ mean > questioning them. Just because a project, company, or group has always > used a particular style, does not mean there are good reasons for the > choices - or that the original reasons are still relevant. Of course > changing the style of existing code, or code added to an existing > project, requires a lot stronger motivation than "I think it looks > nicer" reasoning which is fine for picking your own style for your own > code. > > Style choices - like pretty much anything else in software development - > should not be set in stone. Equally, it should not be changed lightly. Janis