By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,491 Members | 3,132 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,491 IT Pros & Developers. It's quick & easy.

System.Collections.Queue vs. System.Collections.Generics.Queue

P: n/a
Is there any need for "System.Collections.Queue" any more? OK, .Net
made the mistake to start without generics, but that is fixed now.

Languages without support for generics could use
"System.Collections.Generics.Queue<Object>" instead of
"System.Collections.Queue". So everytime those languages use a
generic, they just use them with <object>.

I don't think having two different sets of collections is a good idea.
Nov 22 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Is there any need for "System.Collections.Queue" any more?


Yes, for backward compatibility.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.
Nov 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.