3.4. The Stack Abstract Data Type¶
The stack abstract data type is defined by the following structure and operations. A stack is structured, as described above, as an ordered collection of items where items are added to and removed from the end called the “top.” Stacks are ordered LIFO. The stack operations are given below.
stack<datatype>creates a new stack that is empty. It needs no parameters and returns an empty stack. It can only contain a certain type of data. e.g. int, string etc.push(item)adds a new item to the top of the stack. It needs the item and returns nothing.pop()removes the top item from the stack. It needs no parameters and returns nothing. The stack is modified.top()returns the top item from the stack but does not remove it. It needs no parameters. The stack is not modified.empty()tests to see whether the stack is empty. It needs no parameters and returns a Boolean value.size()returns the number of items on the stack. It needs no parameters and returns an integer.
For example, if s is a stack that has been created and starts out
empty, then Table 1 shows the results of a sequence of
stack operations. Under stack contents, the top item is listed at the
far right.
Stack Operation |
Stack Contents |
Return Value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- 's', 't', 'a', 'c', 'k', 's'
- No, this is valid for a stack. Check the reading for what types of data a stack can have.
- "Stacks"
- No, a stack can have only one item.
- 115, 116, 97, 99, 107
- No, this is valid for a stack similar to A. Check the reading.
- "St", 'a', "ck", 's'
- Yes, stacks should have data of the same type.
Q-1: Which group of data would not make a valid Stack?