Interfaces in Object Oriented Programming

[maddox22]

---

Exactly!

@yanong_banikanhon give it up man! Stop pretending and start learning.

[yanong_banikanhon]

The lesser the dependencies between your software components are the more flexible and reusable they become. Programming against interfaces is one of the best practices you can learn as a developer.

Uyon kaayo ko ani, bay. Ang dili lang gyud insakto kana bitaw'ng mogamit2x ta'g term nga makapasamot og palibog sa mobasa. Unya dili pa gyud nato i-explain. Unsa ma'y purpose sa pag-post kun dili nato ipasabot ang atong gi-post?

Yes, IoC and DI are not actually very difficult to understand if you provide clear explanation. Dili sagol-sagolon ang concepts.

[jonasbelita]

kanis @yanong_banikanhon mailad ra ni ug aplikante nga maayo kaayo mu-memorize. ma-impress gyud ni siya.

pero tama, husto na! peace na ta tanan kay bag-u ra ga simana santa.

bro @yanong_banikanhon peace! i love you!

[yanong_banikanhon]

Again, the main point of IOC is to remove the control from the user class and decoupling your software components making your components flexible and reusable.

This is correct until maddox22 said that the control is transferred to Spring framework. Mao nay makapalibog. That is the reason why I asked those questions. Nothing personal, mga bro. We are all learners here. Let's help each other understand difficult concepts by explaining it properly instead of debating and employing personal attacks.

[kamahak]

Ako gi kalibogan rajd noh ngano ni abot pa mo ug ing-ani na lalis.

I, for one, do not know Java and sa pag-basa nko sa posts dri. Tinuod, wa jd ko kasabot sa mga terms. Daghan kaayo buzzwords gipang gamit. And sa ako nakit-an, ang gusto ra ni @yanong kay ipaklaro lng ug explain ang technical jargon for the benefit of the newbie reader. But instead of a proper and respectful reply, mag ingon2x nuon nga "feeling bright mn ka uy", "ayaw pagtaka2x". Imbis na tarongon ug explain pra makatabang ug tao, mag padak-anay mn hinuon ug itlog. Mu resort mn hinuon ug petty name calling and "kapuy explain nmu, bogo ra kaau ka" type of thinking.

These type of posters really ruin communities like these. Lagi bright ka, dli pd nmu gamiton pra makatabang ug tao. Gamiton hinuon pra mu belittle sa uban. Ug mas maayo pamo niya, ngano inyo mn in-ana-on ug tubag? Ug bright jd ka, ngano dli mn ka civil mu tubag? mag binata mn hinuon.

Bati-a itambay ug in-ani na lugar oi. Ako nabantayan dri noh, any chance to possibly have an intelligent conversation with someone gets shot down with negative comments.

Just wanted to put this out there. On the off-chance that people will start picking up from here.

[jonasbelita]

Kung wala ka kabalo unsa ang actual nga implementation MyWarInterface, dili kaha dilikado nga gamiton ang detonateBomb() method? Given the fact that calling that method could either detonate a bomb under Obama's Desk or under Bin Laden's Bed? Pananglit i-edit sa usa ka malicious user ang configuration file to switch from MyPatriot to MyTerrorist, paskang patayang Obama.

diri man siguro ga-sugod ang panaglalis bai kay sa tao nga gapresentar sa iya kaugalingun nga kamao gyud unya mangutana ug ingani... murag naa may dili insakto ini.

kani nga pangutana klaro man nga wala kasabot sa konsepto. diri gasugod ang init bro. both sides man galabayanay ug insulto. nasakitan man gani ko.. char!

mao lagi dili gyud unta muabot ug ingani. lesson sa ato tanan na lang nga kung dili ta gusto ma-flame sa mga forums din dili lang ta mag-pretend-pretend nga kabalo. mas maayo pa mangutana ug tarung arun tarungun sad ug tubag.

ug murag gitarung man sad ni siya ug tubag ni @canobic pero la ra japon naa gihapon ere nga "sayop ka... be daw be kung kabalo gyud ka...". mayo ni nga leksyon sa ato tanan.

peace na ta tanan!

[yanong_banikanhon]

Kanang panaglalis bay, diha na magsugod kung imong personalon ang mga pangutana. Always remember nga kun mo-post gani ka sa usa ka public forum, duna gyu'y mo-question ana. Busa gani forum ang tawag kay magbinayloay og mga pangutana ug magpaambitay og mga tubag. Dili man ni monologue nga ang speaker ray sige'g yawit. Kun gusto ka'g monologue adto post sa imong kaugalingong blog. Unya i-disable dayon ang comments. Hehe..

Kun duna gani mangutana sa imo unya moinit diretso imong ulo (o mosakit ba kaha ang imong dughan), ayaw na lang og apil2x sa mga forum. Kay ikaw ang mahimong hinungdan sa kamatayon sa usa ka thread. Ganahan ka sa forum nga ikaw ra'y sige'g post?

[fixyourself]

haha, @kamahak right ...

Grabeh kaayo ilang away. Once I had a series of arguments with @yanong_banikanhon, but dili man moabot og away2x.. I guess mo depend sa user if mo acknowledge sya sa skills/knowledge sa ubang posters.

Also, the thread is about interfaces, could we discuss about interfaces in general not specific in java(spring), php. Wala lang.

[silent-kill]

interfaces are useful when you have multiple class having the same methods. e.g

interface IWalkable
 void Walk();

//abstract concepts..
//-------------------------------------
class LivingObject
class Animal :LivingObject
class Insect : LivingObject
class Mechanical

class Dog: Animal, IWalkable
 void Walk(){...}

class Spider: Insect, IWalkable
 void Walk()

class Human : Animal , IWalkable
 void Walk()

class Robot : Mechanical, IWalkable
 void Walk()

calling of the interface in code.

IWalkable walker = WalkerFactory.GetWalker("Human");
walker.Walk(); // action of walking is perform regardless of the original implementation, as long as it implents the IWalkable interface

Each class can implement the Walk method, on each type of animal, there is no restriction on how to implement the method. an interface makes sure that common traits is implemented as a known "interface". like a TV, regardless of its brand you would know how to use it without reading the manual.

now in the real coding world, you don't need to implement interfaces if you don't have different implementations of a certain class. meaning if that class will only have 1 variance you don't need to implement interfaces, i think its overkill.

[yanong_banikanhon]

interfaces are useful when you have multiple class having the same methods. ...an interface makes sure that common traits is implemented as a known "interface". like a TV, regardless of its brand you would know how to use it without reading the manual.

Sakto gyud ni siya, bay.

Ang corollary ani is, kun ang duha ka class dunay managlahi (opposite) nga operations, don't put these classes under a single interface.

Pareha adtong example nga MyPatriot ug MyTerrorist. Sa akong tan-aw sayop nga design kun imo ni silang ibutang sa usa ka interface (i.e., MyWarInterface) kay ang mogamit sa MyWarInterface kinahanglan naman og intimate knowledge sa implementing classes to safely call the detonateBomb() method. In this case, kun dili siya magbasa2x, lagmit mabuthan siya. Hehe...

The fact that an intimate knowledge of the implementation classes is required to call an interface method defeats the purpose of the interface in the first place.