Polymorphism

>>59107443
http://laufer.cs.luc.edu/teaching/313/handouts/practice-midterm

>>59107443
the interface is useful when you want to add a new shape and have all the methods that you must implement already defined so you can just use the interface and know it will work with what ever implements the shape interface

>>59107443
The advantage of polymorphism is that you can have a pointer to a base class but the when you call the function it resolves to the derived class.

Java is really shit for learning programming. The concepts come easier with c++.

>>59108017
using pointers goes against the c++ recommendations

>>59108017
idk, I had a hard time grasping pointers when it was introduced to me (at the time I was learning C++), but I didn't really grasp pointers until I was introduced to objects in Java.

>>59108030
What are you babbling about?

>>59108180
Raw pointers he means. Use smart pointers.

>>59108208
There are still times where it makes sense to use raw pointers. Like as parameters to functions or in any large application where you have long lived objects that are used throughout and have a clear owner of the objects.

>>59108344
No, you should never use raw pointers unless you want to hyper optimized specific functions that bottlenck. Smart pointers should always be used and you should do things OOP for all high level objects, which means doing things the java way.

Think pokemon specifically evee

>>59107972
this

when you start making bigger classes you'll love interfaces

Also why not just have an interface with generic methods at the end of the day only some shapes will share similar get area methods that you'll have to redefine in the first place so any abstract will basically be an overloaded method

>>59108559
Yup. It's the RAIIt™ thing to do

>>59107443
TFW seeing a classmate on 4chan. Hola.

>>59107443
Don't bother, OOP is absolute shit and I immediately forgot everything about after my exam in my OOP course.

If you have to write 50 lines of code and need 3 files to write a very simple hash-function you should abandon whatever you are doing.

>>59107443
In case you are retarded and forget to implement it

File: Ar.K.png (831KB, 843x843px) Image search: [Google]

831KB, 843x843px

>>59107443
Use (((LISP))), problem solved.

>>59108702
surprisingly helpful

File: 1451434814905.png (267B, 400x500px) Image search: [Google]

267B, 400x500px

>>59108559
wrong.
you should never use OWNING raw pointers. non-owning raw pointers are still the preferable way to pass optional function parameters.