You kind of already answered your own question. Dictionary, List, HashTable, etc. There are a lot of collection types in C#, you just have to call the dictionary.remove method with the index instead of doing a pop. It's not really any different other than passing the actual index rather than built in FIFO or LIFO with stacks and queues.
Right, I just didn't want to reinvent the wheel if it wasn't necessary (not that it would be a huge effort - I wrote something in 2 minutes that does the job).
Well, what is hash table that implements a push/pull mechanism on any given key. No such thing in the .NET library. Like I said though, easy enough to implement.
I've actually come to really like Javascript.
The occupations breakdown was surprising. Are only 2.9% of people on stack overflow embedded developers?
I was just looking at that article the other day. Here's a question, how many business applications--specifically those related to Data and Data Manipulation(things easily replaced with relational databases)--are still written in Assembly? I'm starting to feel like I work in the Twilight Zone.The occupations breakdown was surprising. Are only 2.9% of people on stack overflow embedded developers?
Take any c# list and inherit it, then override the get method, or the index accessor. make it so the get method deletes at the end.. boom problem solved.
I'm closer to this reality than you could fathom, or at least would want to.
