code-reuse

We all write reusable classes and code. We factor in configurability to allow us to reuse this fantastic new class again and again. We tell our bosses that spending this extra time now will save us time and money later. But in reality, for those of us who don't write third party libraries, and spend our time working on a application as a whole, how many times does that one class you spent extra time writing to be reused actually get reused in another project? How many bespoke classes do you have in your library which will get used in more than one project? My common rule of thumb is: If you

I would like to write a reusable function I can call within any method to log a snapshot of all the local variables. For example: void somemethod() { int a = 1; string s = "something"; dumpLocalVariables("step 1", MethodInfo.GetCurrentMethod(), this); a++; string t = s + "else"; dumpLocalVariables("step 2", MethodInfo.GetCurrentMethod(), this); } I would like to get a console output like this: step 1 Int32 a = 1 String s = something step 2 Int32 a = 2 String s = something String t = somethingelse I want to avoid providing a specific list of local variable names. The closest I could find was

I have many small files containing code fragments, pseudo-code algorithms, classes, templates, SQL-samples, etc., and I obviously cannot put all these into libraries. I need a practical method to index all of them, and to be able to make this index available to others. What must such an index contain to make searching easiest? Are there any such repositories available on the web? (So I can test the techniques they use.) Are there any applications already written that implement this that I can have a look at? Possible duplicate: https://stackoverflow.com/q/90300/15161 You might want to try

I am trying to find a way to prevent users from double-submitting my forms. I have javascript that disables the submit button, but there is still an occasional user who finds a way to double-submit. I have a vision of a re-usable library that I could create to protect from this. In my ideal library, the code block would look something like this: try: with acquire_lock({'field1':'abc', 'field2':'def'}) as lock: response = #do some credit card processing lock.response = response except SubmissionWasDuplicate, e: response = e.response The lock table would look something like this: duplicate

I would like to add some rounded corners to all of the UIImageViews in my project. I have already got the code working, but am having to apply it to every image; should I subclass UIImageView to add this? If so, can someone give me some pointers as to how to do this? Here is the code - (void)viewDidLoad { [super viewDidLoad]; NSString *mainpath = [[NSBundle mainBundle] bundlePath]; welcomeImageView.image = [UIImage imageWithContentsOfFile:[mainpath stringByAppendingString:@"/test.png"]]; welcomeImageView.layer.cornerRadius = 9.0; welcomeImageView.layer.masksToBounds = YES; welcomeImageView

Any code can be reused in a way or an other, at least if you modify the code. Random code is not very reusable as such. When I read some books, they usually say that you should explicitly make the code reusable by taking into account other situations of code usage too. But certain code should not be an omnipotent all doing class either. I would like to have reusable code that I don't have to change later. How do you make code reusable? What are the requirements for code being reusable? What are the things that reusable code should definitely have and what things are optional? Galwegian See 10