Search Results

Here are some things that may help you improve your code. Eliminate "magic numbers" Instead of hard-coding the constants such as 3, 48 and 55 in the code, it would be better to use a #define or const …

fp)) { perror("couldn't read file"); free(buffer); return 1; } // rest of program here free(buffer); } Consider using standard library functions At a very small performance … Consider using pointers There may not be a performance difference in this case, but for problems like these, the use of pointers seems more natural to me. …

Avoiding the habit of using std::endl when '\n' will do will pay dividends in the future as you write more complex programs with more I/O and where performance needs to be maximized. …

Since you know that all of the non-zero digits must be present in the answer, you can skip most of the numbers in the range. That is, it's pointless to do a test multiplication of 22*3333 because tho …

There might be a slight performance advantage to replicating the code multiple times via a macro invocation, but more often, it just leads to code bloat. …

I see a number of things that could help you improve your code. Don't abuse using namespace std Putting using namespace std at the top of every program is a bad habit that you'd do well to avoid. K …

There are a number of things that could be improved in this code. Post complete code I understand that this code was migrated from Stack Overflow where the rules are a little different, but here on …

Here are some things that may help you improve your program. First, I'll mention a few things about the code you've already written, and then I'll describe an idea for a better algorithm. Be careful …

I see some things that may help you improve your code. Use all of the required #includes The macro SIZE_MAX is used but its declaration is in #include <stdint.h> (not <stdlib.h>) which is not actual …

The code isn't bad, but it's a little more verbose than it needs to be. Consider that we don't really need to check one bit at a time; we can check four simultaneously. The key here is that we're lo …

Here are some ideas to help you improve your code, and perhaps inspire you to learn more. Reconsider using The code currently contains these two lines: using std::cout; using std::cin; That's not too …

I see some things that may help you improve your code. Consider separating input and output Right now, the unscramble function does both the permutation and the printing of both outputs and errors. …

Minimize system calls If you're looking for performance, it's often a good idea to avoid system calls, such as for malloc. …

Unless you really need the stream flushed, you can improve the performance of the code by simply emitting '\n' instead of using the potentially more computationally costly std::endl. …

before and after any changes As with the test function above, you should write many different test functions for your hash and measure their performance. … It's only by actually measuring before and after any change that you will be able to tell for certain whether you are improving or worsening the performance. …