object oriented programming concepts in tamil part5 - message passing

Sdílet
Vložit
  • čas přidán 27. 03. 2018
  • oops concepts message passing in tamil, object oriented programming concepts message passing in tamil, oops message passing in tamil, lets learn understand message passing of oops in tamil, message passing of oops object oriented programming concepts in tamil, tutorial for oops message passing in tamil, quick easy clear intuitive understanding of oops message passing in tamil, object oriented programming message passing for beginners in tamil,better easy understanding of object oriented programming oops message passing in tamil, oops object oriented programming message passing explained in tamil, insight into oops object oriented programming in tamil, oops object oriented programming c++ message passing explained in tamil, oops object oriented programming java message passing in tamil, common man understanding of object oriented programming oops message passing in tamil

Komentáře • 20

  • @bharathidurai9074
    @bharathidurai9074 Před 4 lety +1

    Entha expectation ilama neega video podurathu proud iruku

  • @gowthaman8274
    @gowthaman8274 Před 4 lety

    Unga videos lam Nala iruku inum neraya podunga

  • @senthilmuruganr234
    @senthilmuruganr234 Před 2 lety

    Excellent

  • @JafarAli-wb8bn
    @JafarAli-wb8bn Před 3 lety

    Niga mam book contest tacking pannuga mam kjm use full la Irukum

  • @JafarAli-wb8bn
    @JafarAli-wb8bn Před 3 lety

    Niga mam book contests explain pannuga mam kjm use full Irukum

  • @meenakshisd5398
    @meenakshisd5398 Před 4 lety

    Mam I have a doubt tat message passing is a dot (.) object access which u taught in encapsulation or it's a different one. I can't understand sender recipient and the first one it's damn confusing pls help me.

    • @KamalapriyaSubramanian
      @KamalapriyaSubramanian  Před 4 lety

      The place where obj.method() happens can be the main() function or inside the implementation of a method belonging to some other class, rite? So that place is the one which provides space for obj.method() to happen. That space is called sender or sender object.
      This might seem a bit confusing but if u read and listen properly, you can understand.
      Its like a singing concert happening in an auditorium, say...
      class auditorium
      {
      singing_concert(Singer s)
      {
      s.singing(); //Here a is the sender object and s is the recipient object as far as the method singing() of Singer class is concerned.
      }
      dance_program(Choreographer c)
      {
      c.dancing();//Here a is the sender object and c is the recipient object as far as the method singing() of Choreographer class is concerned.
      }
      }
      main()
      {
      Auditorium a;
      Singer SPB;
      Choreographer Prabhudeva;
      a.singing_concert(SPB);
      a.dance_program(Prabhudeva);
      }
      Here im passing SPB and Prabhudeva objects as an argument to the singing_concert() and dance_program() methods of Auditorium class. If i create the SPB object of Singer class inside singing_concert() method, still it means a is the sender object and SPB is the recipient object on whom the method singing() of Singer class is invoked. Also, main() is the sender as far as singing_concert() and dance_program() methods of Auditorium class are concerned which are invoked on the object a of Auditorium class.
      So, the understanding is that it is the Auditorium object a which provides space for the Singer SPB's singing and Prabhudeva's dancing to happen.
      Suppose we are calling a method inside another method of the same class, we wont be calling like obj.method(). Say for example
      class Samp
      {
      method1()
      { ....}
      method2()
      { .....
      method1(); //Here we are calling using dot because method2 and method1 belong to the same class. Here sender and recipient are the same objects
      }
      }
      main()
      {
      Samp s;
      s.method2(); //s is the recipient-object and main() is the sender. This means method2() is invoked on object s and in due course of control flow method1() is also invoked on the same object s. At that point of execution, the sender method is method2 which is invoked on the same object s. So, in this case the sender and the recipient objects are the same which is nothing but the object s.
      }
      Hope this explanation helps....

    • @meenakshisd5398
      @meenakshisd5398 Před 4 lety

      @@KamalapriyaSubramanian thanks a ton mam.

    • @KamalapriyaSubramanian
      @KamalapriyaSubramanian  Před 4 lety

      Its my pleasure.... You are most welcome...

  • @bharathidurai9074
    @bharathidurai9074 Před 4 lety

    Unmayavay unga video nalla iruku

  • @ganeshvani7271
    @ganeshvani7271 Před 4 lety

    Mam why no vedios nowadays.. pls.. continue your teaching.. pls mam

    • @KamalapriyaSubramanian
      @KamalapriyaSubramanian  Před 4 lety +2

      Sorry ma.... Now-a-days, im busy in many of my personal works and so not able to sit for making videos. But rest of the oops topics, their contents, all are already ready in my mind but videos are yet to be created. Sorry for the delay... Sure i ll resume my videos work soon. Also, i have ideas for videos in other computer engg subject topics too. After finishing oops, i ll create videos for those too.
      Im so happy to know that people await for my educational videos. Thanks for your support and patience...

    • @ganeshvani7271
      @ganeshvani7271 Před 4 lety

      Kamalapriya Subramanian its ok mam. Your teaching is really beneficial for us.. thank you😊

  • @prabu2778
    @prabu2778 Před 4 lety

    Is this PHP oops?

    • @KamalapriyaSubramanian
      @KamalapriyaSubramanian  Před 4 lety

      Its general oops concepts. It may apply to PHP also as PHP is also one of the object oriented languages. I havent worked in PHP but all these concepts would apply for PHP also, probably some minute changes in the language construct...