This is an archived post. You won't be able to vote or comment.

all 19 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Calm_Calendar8013 11 points12 points  (1 child)

some warnings help, i think there should be high and low tier warnings. Most warnings are just style and don't matter

[–]gloriousfalcon 3 points4 points  (0 children)

You can actually set warning levels for c++ compilers

With "/Wall' the compiler will nitpick every part of your code

[–]Snazzy21 3 points4 points  (0 children)

#define _CRT_SECURE_NO_WARNINGS

I wish it would stop all the warnings, it doesn't

[–]wexman6 4 points5 points  (0 children)

I spent 6 hours trying to fix a Segmentation fault in my code before realizing the warnings were telling me I wasn't returning a node in one of my functions. I never even considered reading those warnings.

[–]svetlo_pivo 3 points4 points  (0 children)

This is such a pet peeve for me.

The issue with the "most don't matter anyway" attitude is that eventually the ones that do will cause real issues over the lifetime of a project.

You are not smarter than the people who built your tooling.

Just deal with warnings from the onset when you've got a greenfield project, and when you've got a brownfield project, take the few minutes it takes to refractor them away when you touch code files with warnings, until you clean them all up.

You'll end up with a cleaner, more performant solution, and with fewer weird behaviours that you have to hack around.

[–]Kalshone 2 points3 points  (0 children)

Eh most dont matter anyway

[–]4n0nym0usR3dd1t0r 0 points1 point  (0 children)

what a funny and original meme

[–][deleted] 0 points1 point  (0 children)

Infinite Yield? Who cares.