Lists can do everything that queues can

Question

0.00/5 (No votes)

See more:

As we know, list can be treated as superset of queue(don't go on literal meaning). Like in list we can insert, delete element from anyplace while Queue is the specialized version of list( u can also implement queue using other data structure too). SO why don't we directly use list instead of queue.

Posted 20-Feb-14 22:46pm

Rahul@puna

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Stefan_Lang · Answer 1 · 2014-02-20T22:55:00

Solution 1

Because an API should not allow anything beyond the intended use. If I were to put a function into an API that returns a list as a result that in truth is a queue, then programmers calling that function might assume it's ok to add elements at the top. Whether or not your API documentation warns against that is irrelevant - you can't assume others will read it.

Posted 20-Feb-14 22:55pm

Stefan_Lang

Updated 20-Feb-14 22:57pm

v2

Comments

Rahul@puna 21-Feb-14 5:00am

@Stefan So you are saying that queue is just for specific purpose and it let people know about its behaviour that what it is intended for. That's all why queue is introduced. Am I correct..

Stefan_Lang 21-Feb-14 5:03am

Indeed. There may also be other considerations, such as performance and memory footprint: list implementations are usually bidirective and use two pointer to link with other lements per list element. Queues only need one pointer as they are one-directional. But that is usually of little concern.