[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
I agree with you William. I learnt to program in the 1960s and have used more than thirty languages. My preference for much of that time has been for C and Assembly. My programming has been as a scientist and also as a freelance developer, and so never worked for a software house. So I got to choose the language myself. When C++ came out, I looked at it, realised it obfuscated everything so that memory problems could easily occur if not careful, and so stuck firmly with C and Assembly. I am aware that those memory problems caused the development of various systems for eliminating such errors, and have been considering teaching myself C++ in my old age. The problems caused by the obfuscation should disappear if you understand fully what you are doing, and use the right tools to give code integrity. Helen McCall On Thu, 18 Sep 2025 23:26:01 +0100 WaiTsun Yeung <williamywt0624@xxxxxxxxx> wrote: > I used to scoff at the narrative until I have started working at a > decades old company led by senior programmers who only know how to > write pre-C++11 code; and throw around the new keyword without > bothering if those pointers are updated or deleting properly until > the program coughs up a segfault. > > C++ is an old language, yes, old C++ is more prone to memory and > security vulnerabilities owing to the relative lack of convenient > syntax and development tools back then, but it shouldn't be a problem > for new code as long as the developers have static code analysis > turned on and an up-to-date development guide to follow. Code > developed this way won't be visibly more bug-prone than code > developed in other languages. > > When unsafe code keeps being unsafe code in the modern days, it's > usually the fault of tech leads whom are either not knowledgeable > enough or hasn't grown a spine to keep technical debt down. Switching > to other languages may makes things slightly easier but won't save > their skin in the long run. > > *Best regards,* > *William (he/his/him)* > *~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~* > *If you find this email at any odd hour, weekend, or holiday, it is > because it works with my schedule at this time of the week or because > I am sending it from the opposite end of the Earth. **So that** you > know, you are not expected to reply outside *regular* working hours!* > > 2025年9月18日(木) 19:33 zleap via list <list@xxxxxxxxxxxxx>: > > > Hi All > > > > The link was posted to Mastodon today. > > > > I just thought I would share this here, as I know there are users > > of c,c++ and probably Rust too. > > > > C++ creator calls for help to defend programming language from > > 'serious attacks' > > > > https://www.theregister.com/2025/03/02/c_creator_calls_for_action/ > > > > As I am not an expert at this, but I am aware of c++ memory issues > > and that Rust seems better in that respect. What people here think > > of this. > > > > Paul > > -- > > Paul Sutton > > https://zleap.net/ > > -- > > The Mailing List for the Devon & Cornwall LUG > > FAQ: https://www.dcglug.org.uk/faq/ > > -- The Mailing List for the Devon & Cornwall LUG FAQ: https://www.dcglug.org.uk/faq/