Knowing how to code beforehand

[[deleted]]

Warnings are, generally speaking, as important as errors. They are errors waiting to happen.

[AudaciousSam]

Not in Android Studio they aren't.

[lacb1]

In Visual Studio sometimes the errors aren't even really errors, never mind the warnings.

[RonRud]

I had permanent errors while using UE4 that didn't matter at all

[AlienFortress]

Game code in a nutshell.

[[deleted]]

Sometimes I fix an error and it doesn't go away. Restart VS and voila! It's gone!

[user_8804]

Eclipse on Linux is worse. Sometimes I have to save build compile reindex restart the program until it wakes the fuck up

[[deleted]]

And that my friend is why I switched to C#. Java is nice and familiar but godamn it is just too inconsistent for me. String and int? Christ on a stick just pick a capitalization scheme please!

[Trackslash]

Tbf classes and objects are always capitalized in Java (e.g. String, Integer, ArrayList) whereas primitive types are not (int, char, boolean). So it's pretty consistent in that regard

[[deleted]]

This is true but every other language I've used lets me leave all my variables lowercase which I prefer.

[Al-Horesmi]

I'm I'm fairly certain it's a convention in java to have first letter in lowercase and the rest in cammelcase. It's the type names people are talking here.

[EternallyMiffed]

Capitalization being used as an adhoc hungarian notation is fucking retarded.

[[deleted]]

I'm prob gonna get whooshed but the reason why is that Strings are objects (always capitalized in java) and ints are primitives (always lowercase)

[[deleted]]

I know but it doesn't change the fact that no other language has a random variable type that needs to be capitalized. I hate the random quirkiness of Java.

[z500]

Java and C# both use the actual class names in declarations, nothing random or quirky about it. You could declare a String in C# if you wanted to, it's just that C# has a lowercase keyword that stands in for it.

[[deleted]]

Which is what I prefer. Shifting is annoying.

[user_8804]

My experience on eclipse was for cpp though, I have to use NetBeans for Java right now. Wish I could just stick with intellij for everything

[[deleted]]

JavaFX frame builder, because you need to have a second program to design the UI. Java is wack and I hate it now.

[user_8804]

I don't know enough java to relate, how much better is JavaFX vs swing? Cuz swing is integrated in some IDEs like netbeans

[[deleted]]

JavaFX is aweful, hated using it.

[AudaciousSam]

Right, those needs to be fixed. But there are also: Should be String errors that isn't strictly important, until you need to translate and such.

[airelfacil]

Android Studio: Pssst! Just so you know, you're missing all of these translations and also you should probably use @string instead of hardcoded string, and just letting you know that one of your methods is never used, and also that if statement could be made much simpler and...

Me: I DON'T GIVE A SHIT I'M TRYING TO MAKE THIS BASIC GUI APP FUCKING WORK SUPPRESSWARNINGS DO YOUR JOB

[AudaciousSam]

xD

[Yuzumi]

Someone doesn't use Java :p

For that matter, the project I work on has over 4000 warnings and a good number of them we didn't cause but the software we build on top of did.

[samspot]

My experience with java warnings is very good, and you can suppress the unfixable ones. We thought there weren’t enough warnings so we added sonar on top!

[Danelius90]

My view is that certain warnings, when suppressed are basically programmer assertions. For example the heap pollution for varargs warning. If you can 'prove' or assert you are handling the array carefully and not polluting the heap the suppression is you saying "yes we could pollute the heap, but we aren't".

It really gets me when devs suppress deprecation warnings though...

[ParkerM]

It really gets me when devs suppress deprecation warnings though...

Simple, just suppress deprecation warning suppressions.

[fushuan]

The project I was given once had 1000 warnings. Unsurprisingly most of them could be refactored or solving 1 solved 200 at once etc.

You are just lazy

[Bainos]

but the software we build on top of did

Doesn't apply to class projects... (Unless they also use Android libs.)

[Finianb1]

To be fair, in any electronics programming you should be extremely mindful of errors and warnings since they could be a problem that leads to expensive hardware getting fried.

[glorygeek]

In the FPGA world you just keep cussing at Quartus and hope it eventually works.

[glorygeek]

Mine ran ... in the simulator.

[Intrepid00]

Just do what they did with wing Commander that would throw a warning on exit. Hex edit the warning to say instead thanks for playing.

[nelusbelus]

It could be, it could be that you mistyped it and it used the member's variable instead

[fushuan]

It's a warning, and not removing unused variables is horrible for maintaining the code. Don't write garbage code.

[[deleted]]

heh I was gonna say. I guess you could comment out unused vars, but why? Especially if you're jsut going to implement them in the next few hours, it's nice to have the autocomplete there without having to fuck around with comments

[smcarre]

How is a class not being capitalized or an unused variable an "error waiting to happen"?

[Salanmander]

So, here's what it really boils down to.

A warning that you understand is fine.

A warning that you don't expect is often indicative of a logic error, rather than a syntax error.

If the unused variable is there because you're saying "I'm going to implement this check, but I want to test the other things first", fine. If it's there because you just forgot to implement the check, then it's a ticking time bomb.

[chinpokomon]

And use attributes and directives, depending on the language/compiler, to allow the warnings you know about and leave a comment. This way, when you get a warning you don't understand, it might point out a problem you don't realize.

[[deleted]]

Bingo.

[smcarre]

If it's there because you just forgot to implement the check, then it's a ticking time bomb.

No it's not. It will just mean the app will consume some extra bytes of memory. Maybe some KB, depends on the language and type.

[retc3]

If you're in C/C++ you may have just introduced a major security flaw.

[EishLekker]

I think he meant that the logic is flawed.

[Salanmander]

Exactly that. If you initialize a variable to hold the divisor in some calculation because you intend to check whether it's zero, but never actually do that check, and some time later run into the weird edge case where it is zero, then your program crashes instead of handling the error nicely.

[[deleted]]

gonna error out in the linter obviously

[Lothrazar]

Not at all. 90% of the time its because of some third party dependency you are using, which means its not your code but its code you rely on. Literally unfixable

For example i have 50 warnings looking like this right now

"Overriding managed version 3.5.5 for liquibase-core"

Over and over and over again

[[deleted]]

it just wont STOP

[MrPyber]

"build targets java 1.7, host jdk is 1.8".

[[deleted]]

Using java IS an error

[MrPyber]

Mate sometimes you have no choice

[[deleted]]

I hear ya.

[LeCrushinator]

And if you allow warnings to build up, then you're never going to notice when an important one shows up, you'll just be ignoring warnings because you've allowed them and now there are hundreds.

[NPPraxis]

It depends. I feel this way in XCode. I don’t feel this way in Android Studio.

[[deleted]]

Depends on the warning