This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
personally, i would comment all of them out but one, and implement it first. implement it, test it, test it some more, then test it again. Note that when testing, you often have to write 'throw-away' code - code that is used ONLY for testing, but won't then be in your final program.
Which method you do first is sort of dependent on a few things. You can't really test your clear() method if there is nothing in the collection, so it doesn't make sense to implement it first...and Rob is right - your put() method has problems.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: I want to know how to use methods furnished below in this program???