Q re Bridge Design Pattern - Abstract Classes vs Interfaces

  • Thread starter Thread starter Simon Woods
  • Start date Start date
S

Simon Woods

Hi

I'm just working through (and learning) the standard GoF Design Pattern and
the example of the Bridge pattern on
http://www.dofactory.com/Patterns/PatternBridge.aspx#_self2

I notice at the heart of the real world example is an abstract class

MustInherit Class DataObject
Public MustOverride Sub NextRecord()
Public MustOverride Sub PriorRecord()
Public MustOverride Sub NewRecord(ByVal name As String)
Public MustOverride Sub DeleteRecord(ByVal name As String)
Public MustOverride Sub ShowRecord()
Public MustOverride Sub ShowAllRecords()
End Class

which gets inherited by another class CustomerData which populates itself
with various customers.

I'm wondering why an abstract class is used here rather than an interface.

Could someone help me out pls?

Thanks

Simon
 
Simon Woods said:
Hi

I'm just working through (and learning) the standard GoF Design
Pattern and the example of the Bridge pattern on
http://www.dofactory.com/Patterns/PatternBridge.aspx#_self2

I notice at the heart of the real world example is an abstract class

MustInherit Class DataObject
Public MustOverride Sub NextRecord()
Public MustOverride Sub PriorRecord()
Public MustOverride Sub NewRecord(ByVal name As String)
Public MustOverride Sub DeleteRecord(ByVal name As String)
Public MustOverride Sub ShowRecord()
Public MustOverride Sub ShowAllRecords()
End Class

which gets inherited by another class CustomerData which populates
itself with various customers.

I'm wondering why an abstract class is used here rather than an
interface.
Click to expand...

I wonder, too (not knowing the book). Maybe the base class will be extended
by "content" in the following chapters? Otherwise, I'd probably choose an
Interface.


Armin
 
I'm wondering why an abstract class is used here rather than an
interface.
Click to expand...

I guess it gives more flexiblity in the future - you can always extend the
base class with additional features easily (i.e. base implementations).
With an interface, you would need to update the entire project.
 
Back
Top