Hey,
I'm building a repository of solutions. If you want to share your AC solutions then please do so. You can also share other IT knowledge on my site and you are encouraged to do so, i.e. algorithms and methods, really just about anything that is IT related.
Please remove your author ID from your source if you upload it, just so you won't get unwanted emails from people trying your code. Also, please remove unnecessary comments.
Just register here: http://itnoise.com
Then follow the file galleries link.
Mostly looking for c or cpp source.
Thanks,
Jason
Solution Repository
Moderator: Board moderators
For the algorithms part (and probably also for UVa solutions), don't reinvent the wheel and rather contribute to the existing http://algorithmist.com/
Plus, I like its way (posting primarily the solution idea, NOT the source code) much better.
Plus, I like its way (posting primarily the solution idea, NOT the source code) much better.
Thanks Misof. The concept of posting only the algorithm is certainly a good approach to helping people. However, for a lot of the UVA problems the algorithm is the easy part, actually producing the code is harder, especially when you may be restricted to a certain language. The idea is just for people to see a lower level approach to the problem and to get an idea of how someone else solved the problem because there can be many approaches to the same solution.
Thanks for your reply.
Thanks for your reply.
It would be unwise to upload ready to submit source code, because there are plenty of code collectors out there who merely submit these codes. In past there were few sites like this, but due to requests and from the results of polls, the site admins decided to stop publishing source code.j_hines wrote:Thanks Misof. The concept of posting only the algorithm is certainly a good approach to helping people. However, for a lot of the UVA problems the algorithm is the easy part, actually producing the code is harder, especially when you may be restricted to a certain language. The idea is just for people to see a lower level approach to the problem and to get an idea of how someone else solved the problem because there can be many approaches to the same solution.
Thanks for your reply.
But as you have said, certain solutions are better understood by looking at source code rather than algorithm description, those solutions may be published.
thanks for your reply.
You make a good point. Code collectors really have nothing to prove though by increasing their numbers, it's just that, a number, it doesn't carry much weight. The repository would be more geared toward teams who are actually practising to qualify for regionals or worlds, sort of a last resort.
You make a good point. Code collectors really have nothing to prove though by increasing their numbers, it's just that, a number, it doesn't carry much weight. The repository would be more geared toward teams who are actually practising to qualify for regionals or worlds, sort of a last resort.