[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: catbag.jpg (140 KB, 750x728)
140 KB
140 KB JPG
You actually read the warning messages and try to fix them right anon?
Yes, even in C. Especially in C. I've never gotten a segfault in C when treating warnings as errors.
>>
Meanwhile in java land you ingore the warnings *and* the errors and hope it compiles somehow anyway
>>
>>106450977
Yes, warnings make the PR icon orange which is bad. I fix the formatting too for the same reasons. I do this for nightly tests and lints too, for the same reason.
>>
>>106450977
Of course, it's best practice.
You can have warnings happen during development, but release should never have warnings.
>>
>>106451058
>>106453503
Racial status confirmed, white
>>106452748
Asian
>>
>>106450977
-Wall -Wpedantic my beloved
>>
>>106450977
Occasionally I run into situations where a style warning is just legitimately the behavior I need (a function that accepts but never uses an argument because it's going to end up passed as a function pointer and needs to match the expected form, for example), but otherwise yeah.
>>
>>106450977
Absolutely.
Sure, if it's like, an unused variable, that might happen durring some phases of development, but actual warnings? They're at least worth looking into.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.