Since I don't have 50 years of free time to read the entire man page, was just wondering how you exclude warnings in the output so you only see the errors? Useful for when you have like 300 warnings and 1 error. For some reason grep doesn't help...
Since I don't have 50 years of free time to read the entire man page, was just wondering how you exclude warnings in the output so you only see the errors? Useful for when you have like 300 warnings and 1 error. For some reason grep doesn't help...
So do we.
The warnings are all acceptable, I have read them and taken them into account. I'm tired of reading them, would be great not to have to write some script or long command to get around this... The reason for all the warnings is this is a program with thousands of lines.
> The warnings are all acceptable,
And you know this how?
What happens when warning 301 comes along which is NOT OK for you to ignore? You're already aiming to remove them all from sight.
> The reason for all the warnings is this is a program with thousands of lines.
Bully for you. My current project is >100K lines, and the number of warnings is typically zero.
If the baseline is zero, it is VERY easy to spot when something new appears, because it will be the ONLY thing in view.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
It's a class project we're not writing a new distribution of the Linux operating system or anything. In any case, I demoed my project this morning and it fulfilled all the requirements, so I don't think the warnings were impacting anything.Originally Posted by Salem
I suppose that depends how bad of a programmer you want to be...
Nobody's perfectI am improving tho
