Liste des Groupes | Revenir à cl c |
David Brown <david.brown@hesbynett.no> writes:There's nothing wrong with preferences - whether it be for comment style or a chosen editor / IDE.
On 25/02/2025 17:52, Ar Rakin wrote:I actually prefer /* */ comments over // comments. There is no specificOn 2/25/25 10:28 PM, David Brown wrote:>>I agree! The C projects that I have built use latest C features. I
And for your own code, don't be afraid to find a better way of
writing your code. You don't have to be restricted to a C standard
that was replaced a generation ago. You don't have to limit
yourself to code that was designed to work well with computers,
software and screens from four decades ago.
usually always use the `-std=gnu17` or `-std=gnu23` compiler
flag. (Yes, I do use the GNU C extensions often.)
In that case, use // comments instead of /* */ comments when it makes
sense. Use line layout that makes sense and suits /your/ usage -
don't use a layout for function definitions based on what some ancient
editor liked unless you also like that ancient editor, or you like
that layout. Pick a tab size that suits /your/ preferences for
coding, using tab characters or spaces for whatever works best with
/your/ choice of tools.
reason for this, I just tend to like it that way. And yeah, I use Emacs,
you *might* say it is ancient but I love Emacs.
Les messages affichés proviennent d'usenet.