If you are using clang-format in any of your projects, this might be useful to apply complex .clang-format rules as you type rather than after-the-fact.
@chandlerc thank you! And no, I'm not aware of any similar efforts unfortunately. That doesn't mean they don't exist though! Which editor were you hoping for?
@aka_pugs I wrote quite a lot of code in BCPL when a few of us were working (in our spare time) on a port of the Cambridge University Tripos operating system to a 68010 based machine called the Image 10, back in the 1980’s.
Trust the #programmer. Generally speaking, the #C language assumes you know what you’re doing and lets you. This isn’t always a good thing (for example, if you don’t know what you’re doing).
Don’t prevent the programmer from doing what needs to be done. Because C is a system #programming language, it has to be able to handle a variety of low-level tasks.
Keep the language small and simple. The language is designed to be fairly close to the hardware and to have a small footprint.
Provide only one way to do an operation. Also known as conservation of mechanism, the C language tries to limit the introduction of duplicate mechanisms.
Make it fast, even if it isn’t guaranteed to be portable. Allowing you to write optimally efficient code is the top priority. The responsibility of ensuring that code is portable, safe, and secure is delegated to you, the programmer.
Si vous connaissez quelqu'un qui connaît quelqu'un qui a son oncle qui connaît quelqu'un dont le voisin recherche quelqu'un pour un poste de développeur soit web soit c++ (+ Qt éventuellement) je suis preneur. Boosts appréciés #CPP#CLang#Qt#Dev#C++ #C#Web#HTML#PHP#JS#CSS#Travail#Job
Hello. You can call me @modev. I would like to write free #software, but I've been writing commercial software for 20 years to make a living for my family. I have been interested in #programming since childhood for about 25 years. I started with BASIC, Pascal, and even started learning :clang: #clang, but then switched to more “advanced” technologies. As a result, I found a job as a web #developer while still at university, where I still work. I am a JavaScript master, I created my own SPA Ajax framework from scratch back when React and Angular were not in the project, but who is interested in this, except for the company I work for? As a result, I, burned out many times, rising from the ashes of commercial development and all this crap, decided to return to the roots and teach :clang:. All I can do now is to believe that I will still make my contribution to the #development of free software, but for now I’m glad to be in your #community and learn new things, this is the only way I can save myself from burnout. Thanks everyone!
I could have written this way, but I decided not to do it there, having registered in the newly created community#writefreesoftware. Thank you, @drewdevault for creating it!
Wow, that's sad to hear. For some reason, that spared me. However, despite a bit working with Python+Flask, I never was in webdev. I went into systems programming, like Linux Kernel, Linux images, Linux apps in C, C++/Qt, Bootloader, Embedded. Hardware Drivers. I did some FOSS work (like upstream driver work for the Linux kernel, or patches to Barebox, or being one of the 4 founders of #OpenEmbedded) ... but like you I mostly did "behind the doors" code to pay my family and house.
But nothing of this ever touched my mental health.
I however heard several times from burnout of WebDevs. Do you think this is just by coincidence... or is there something in the WebDev industry that is gnawing on people's health?
Personally, I have nothing against the emergence of new #programming languages. This is cool:
the industry does not stand still;
competition allows existing languages to develop and borrow features from new ones;
developers have the opportunity to learn new things while avoiding #burnout;
there is a choice for beginners;
there is a choice for specific tasks.
But why do most people dislike the :clang: #clang so much? But it remains the fastest among high-level languages. Who benefits from C being suppressed and attempts being made to replace him? I think there is only one answer - companies. Not developers. Developers are already reproducing the opinion imposed on them by the market. Under the #influence of hype and the opinions of others, they form the idea that C is a useless language. And most importantly, oh my god, he's unsafe. Memory usage. But you as a #programmer are (and must be) responsible for the #code you write, not a language. And the one way not to do bugs - not doing them.
Personally, I also like the :hare_lang: #harelang. Its performance is comparable to C, but its syntax and elegance are more modern.
And in general, I’m not against new languages, it’s a matter of taste. But when you learn a language, write in it for a while, and then realize that you are burning out 10 times faster than before, you realize the cost of memory safety.
Personally, I also like the :hare_lang: #harelang. Its performance is comparable to C, but its syntax and elegance are more modern.
That exactly why I like #nimhttps://nim-lang.org/ --- it's IMHO much more mature than Hare and offers more targets (e.g. compile to C, C++, JavaScript, WASM or various embedded devices).
@holgerschurig I also started with nim, yes it's the best of new languages, but Python syntax... I am using C-like languages in everyday work and switching is tiring.
I'm trying to fix a patch to allow #pixman's #ARM#NEON#assembly code to build with clang. They perform a lot of mechanical changes to switch to the "unified" ARM assembly syntax (.syntax unified), supported by both #gcc and #clang.
With clang the code builds but fails 3 of the tests in the test suite with what appear to be unaligned accesses. With gcc, the test suite passes before and after the patches.