Language:
switch to room list switch to menu My folders
Go to page: First ... 31 32 33 34 [35]
[#] Thu Oct 18 2018 09:16:55 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


It's generally a good idea to address compiler warnings where possible, if you're the guy writing the code.

[#] Thu Oct 18 2018 11:30:41 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

It's an arms race between developers who try to fix code that generates compiler warnings, and compiler developers who find new things to warn about.

[#] Thu Oct 18 2018 13:15:48 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Sometimes.

I've also had warnings help me find problems that might have come up in some obscure run of the software that would have had me scratching my head for hours to figure out.

These days, I pay attention to the warnings in my code, and try to modify it to make the warning go away (or add comments to it to explain that the warning was considered and should be ignored). At least, I have found it works for me.

Go to page: First ... 31 32 33 34 [35]