TIFU by not using objects in my object-oriented programming coursework
TIFU by not using objects in my object-oriented programming coursework
You're viewing a single thread.
But answer07 is an object... Not sure what your teacher/ta disliked 😆
I presume WeatherData.getData() should be going into some Data class that has multiple properties (using the , as a delimiter) instead of what OP is doing and just using the String
I mean, unless it's explicitly specified, one can still argue. For fun, that is. I did it a few times with stuff like using maps when the task said I couldn't use loops. Didn't really get into trouble since there was a proper solution ready as well.
This is one condition in which I might like the "If it runs, you get marks" examiners
To be needlessly pedantic on this joke, answer07 in itself is not an object, but a class, a blueprint for objects. An instance of that class would be an object. Calling the static function main does also not create an instance of the class in the class loader.
To expand on that you can never instantiate an object of type answer07 since it's a static class.
(For the students here the "static" modifier means "it's on the class, not the object". Non-static will only be accessible as a "obj.whatever" but static is accessible by "Class.whatever")
Is the class declared static? I assume the "...ic class Answer07" at the top stands for "public class Answer07".
I don't think java supports top level static classes (it does have nested static classes, though).
Oh, I haven't handed it in yet. We were supposed to write our own methods.
So really it's in a few days iwfu(I will fuck up)