Bookmark Topic Watch Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Report post to moderator
I removed the following from InterfaceVsAbstractClass, because I didn't understand it and suspected that it might be more confusing than of help. I would appreciate some clarification on what was meant by the statement - hopefully we can find a more clear wording.



If you think that there is some generalized concept to be followed by the other classes go for abstract classes. But if you think that there is nothing general (i.e. may be a business requirement) then go for interfaces only.



Abstract Classes can have method implementations in addition to method signatures. Interfaces have only method signatures - they do not allow method implementations.

Abstract Class have Concrete Method .But In Interface Only abstact method and Public Method.
 
Everybody's invited. Even this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
    Bookmark Topic Watch Topic
  • New Topic