Skip to main content
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Source Link

This is a refactored version of the code presented in Recursive Breadth First Search for Knights Tour.

This is a refactored version of the code presented in Recursive Breadth First Search for Knights Tour.

Bumped by Community user
Moved GitHub link into question. Moved requested reviewed items up. Changed the order of what I wanted reviewed.
Source Link
pacmaninbw
  • 24.8k
  • 11
  • 46
  • 109

ThisThe development and testing was doneperformed on a Dell M6400 Laptop (Intel Core 2 Duo) running Centos 7, g++ compiler version 4.8.5, compiler switches -O3 -std=c++0x -D__cplusplus=201103L. (machine bought August 2009 with Windows XP ). It was also tested on a four core i7 based version of CentOS 7 with 12GB of DDR3 RAM (built 2011).

The code, makefile and gz compressed gprof output are posted on GitHub.

This is a refactored version of the code I presented in Recursive Breadth First Search for Knights Tour.

I refactored the code for several reasons:Please make any and all suggestions on improvement, I am especially interested in the following

  1. Are the any Containers or Library Algorithms in C++11 that would have decreased the amount of code or improved the quality of the code?
  2. Improving readability
  3. Improving maintainability
  4. Improved Data Encapsulation.
  5. Reducing coupling between classes as much as possible.
  6. More optimization (speed freak).

The code was refactored several reasons:

I am open to all suggestions on improvement, I am especially interested in

  1. More optimization (speed freak).
  2. Improved Data Encapsulation.
  3. Reducing coupling between classes as much as possible.
  4. Improving readabilty
  5. Improving maintainability
  6. Are the any Containers or Algorithms in C++ that would have decreased the amount of code, that I should have used?

I am representing allAll classes are presented, but the classes that changed the most are first.

This development and testing was done on a Dell M6400 Laptop (Intel Core 2 Duo) running Centos 7, g++ compiler, compiler switches -O3 -std=c++0x -D__cplusplus=201103L. (machine bought August 2009 with Windows XP ).

This is a refactored version of the code I presented in Recursive Breadth First Search for Knights Tour.

I refactored the code for several reasons:

I am open to all suggestions on improvement, I am especially interested in

  1. More optimization (speed freak).
  2. Improved Data Encapsulation.
  3. Reducing coupling between classes as much as possible.
  4. Improving readabilty
  5. Improving maintainability
  6. Are the any Containers or Algorithms in C++ that would have decreased the amount of code, that I should have used?

I am representing all classes, but the classes that changed the most are first.

The development and testing was performed on a Dell M6400 Laptop (Intel Core 2 Duo) running Centos 7, g++ compiler version 4.8.5, compiler switches -O3 -std=c++0x -D__cplusplus=201103L. (machine bought August 2009 with Windows XP ). It was also tested on a four core i7 based version of CentOS 7 with 12GB of DDR3 RAM (built 2011).

The code, makefile and gz compressed gprof output are posted on GitHub.

This is a refactored version of the code presented in Recursive Breadth First Search for Knights Tour.

Please make any and all suggestions on improvement, I am especially interested in the following

  1. Are the any Containers or Library Algorithms in C++11 that would have decreased the amount of code or improved the quality of the code?
  2. Improving readability
  3. Improving maintainability
  4. Improved Data Encapsulation.
  5. Reducing coupling between classes as much as possible.
  6. More optimization (speed freak).

The code was refactored several reasons:

All classes are presented, but the classes that changed the most are first.

Tweeted twitter.com/StackCodeReview/status/746106329215950852
Changed the chess tag to C++
Link
pacmaninbw
  • 24.8k
  • 11
  • 46
  • 109
Reduced the size of the question by removing output and differences.
Source Link
pacmaninbw
  • 24.8k
  • 11
  • 46
  • 109
Loading
properly formated output, removed differences in KLOC
Source Link
pacmaninbw
  • 24.8k
  • 11
  • 46
  • 109
Loading
Source Link
pacmaninbw
  • 24.8k
  • 11
  • 46
  • 109
Loading