Ad:

C++ Discussion Thread
Unsolved
Views: 2089

Sep 25th, 2007

Stack Abstract Data Type Question

Expand Post »

Sorry~~, I don't know where to post this quetion.

Can someboy help me with this question, plz....

Suppose someone designed a stack abstract data type in which the top function returned an access path (or pointer), rather than returning a copy of the top element. This is not true data abstraction. Why?

Similar Threads

Working with SQL server's Image data type in ASP.NET
C++: problam with data type(int,float,double) in C++
help understanding "char" data type in C++
Problems with changing values returned by RegQueryValueEx in C
help on data type conversion in Visual Basic 4 / 5 / 6

jack223

Reputation Points: 10

Solved Threads: 0

Light Poster

Offline

27 posts
since Nov 2005

Permalink

Sep 25th, 2007

Re: Stack Abstract Data Type Question

>This is not true data abstraction.
Sure it is. The abstraction is the stack and its implementation, not the contents of the stack. Returning a copy of the top of the stack instead of a pointer to it makes no difference in how the stack works. Presumably the question is assuming that a malicious coder can break umpteen language rules to get a hold of other items if given a pointer to one item, but that's equally likely with nothing more than a stack object regardless of how much abstraction you put into it.

Narue

Administrator

Reputation Points: 6442

Solved Threads: 1393

Bad Cop

Offline

11,807 posts
since Sep 2004

Permalink

Sep 25th, 2007

Re: Stack Abstract Data Type Question

It's certainly poor encapsulation.

Giving someone a pointer to the innards of your class exposes you to all sorts of problems. What if they try to write to your class data via the pointer? What if they increment the pointer, where does it point to then?
Applying all sorts of const to the result can only go so far.

Yes, std::string has the c_str() method which returns a pointer to something on the inside, but that's more a "necessary evil" rather than an example of good design IMO.

Salem

Team Colleague

Reputation Points: 5862

Solved Threads: 950

Posting Sage

Offline

7,164 posts
since Dec 2005

Permalink

Sep 25th, 2007

Re: Stack Abstract Data Type Question

very often, encapsulation/insulation and efficiency pull in opposite directions. and c++ programmers have to do a fine balancing act between the two and decide what is most appropriate in a particular case. for example,

C++ Syntax (Toggle Plain Text)
struct book // fully insulated, least efficient
{
  book( const atring& t, const list<string>& a, const string& n ) ;
  book( const book& ) ;
  book& operator=( const book& ) ;
  ~book() ;
  string title() const ;
  list<string> authors() const ;
  string isbn() const ;
  // ...
  private:
    struct implementation ;
    implementation* opaque_pointer ;
};
struct book // fully insulated, least efficient
{
  book( const atring& t, const list<string>& a, const string& n ) ;
  book( const book& ) ;
  book& operator=( const book& ) ;
  ~book() ;
  string title() const ;
  list<string> authors() const ;
  string isbn() const ;
  // ...
  private:
    struct implementation ;
    implementation* opaque_pointer ;
};

C++ Syntax (Toggle Plain Text)
struct book // encapsulated, partially insulated
            // more efficient 
{
  book( const atring& t, const list<string>& a, const string& n ) ;
  book( const book& ) ;
  book& operator=( const book& ) ;
  ~book() ;
  string title() const ;
  list<string> authors() const ;
  string isbn() const ;
  // ...
  private:
    string _title ;
    list<string> _authors ;
    string _isbn ;
    // ...
};
struct book // encapsulated, partially insulated
            // more efficient 
{
  book( const atring& t, const list<string>& a, const string& n ) ;
  book( const book& ) ;
  book& operator=( const book& ) ;
  ~book() ;
  string title() const ;
  list<string> authors() const ;
  string isbn() const ;
  // ...
  private:
    string _title ;
    list<string> _authors ;
    string _isbn ;
    // ...
};

C++ Syntax (Toggle Plain Text)
struct book // encapsulated, not insulated
            // even more efficient (inlining)
{
  book( const atring& t, const list<string>& a, const string& n ) ;
    : _title(t), _authors(a), _isbn(n) { /* ... */ }
  string title() const { return _title ; }
  list<string> authors() const { return _authors ; }
  string isbn() const { return _isbn ; }
  // ...
  private:
    string _title ;
    list<string> _authors ;
    string _isbn ;
    // ...
};
struct book // encapsulated, not insulated
            // even more efficient (inlining)
{
  book( const atring& t, const list<string>& a, const string& n ) ;
    : _title(t), _authors(a), _isbn(n) { /* ... */ }
  string title() const { return _title ; }
  list<string> authors() const { return _authors ; }
  string isbn() const { return _isbn ; }
  // ...
  private:
    string _title ;
    list<string> _authors ;
    string _isbn ;
    // ...
};

C++ Syntax (Toggle Plain Text)
struct book // less encapsulated, not insulated
            // most efficient (no copy of objects)
{
  book( const atring& t, const list<string>& a, const string& n )
    : _title(t), _authors(a), _isbn(n) { /* ... */ }
  const string& title() const { return _title ; }
  const list<string>& authors() const { return _authors ; }
  const string& isbn() const { return _isbn ; }
  // ...
  private:
    string _title ;
    list<string> _authors ;
    string _isbn ;
    // ...
};
struct book // less encapsulated, not insulated
            // most efficient (no copy of objects)
{
  book( const atring& t, const list<string>& a, const string& n )
    : _title(t), _authors(a), _isbn(n) { /* ... */ }
  const string& title() const { return _title ; }
  const list<string>& authors() const { return _authors ; }
  const string& isbn() const { return _isbn ; }
  // ...
  private:
    string _title ;
    list<string> _authors ;
    string _isbn ;
    // ...
};

;

Last edited by vijayan121; Sep 25th, 2007 at 11:03 pm.

vijayan121

Reputation Points: 1159

Solved Threads: 285

Posting Virtuoso

Offline

1,606 posts
since Dec 2006

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.

Previous Thread in C++ Forum Timeline: what wrong with this code block?

Next Thread in C++ Forum Timeline: Some math and MFC

DaniWeb Message

Cancel Changes

User Name
Password