Concept

[MilchRatchet]

Here are some concepts for this project, you can add or suggest changing these if you want.

• Source files and header files simply reside in the corresponding folder (eg. AAL/). The header files are copied to the output folder when building.
• You may use C++. If you do, the source file should be *.cpp, the header should be *.h. The signature of the function should be C valid, i.e. inputs may not be instances of classes etc. Functions should be extern "C" and in the header file this should be declared conditionally based on if cpp is defined.
• Each problem gets its own file, this way each file will contain a collection (though sometimes just one) of algorithms regarding one problem.
• Functions should be named {LIBRARY}_{PROBLEM}_{ALGORITHM} where {ALGORITHM} may be left out if there is only one algorithm for a given problem. For example AAL_KNAPSACK.
• No intrinsics etc, in this project I would prefer compatibility over speed. I would guess that for most algorithms here the compiler will do a good enough job anyway.
• At first we may simply commit to master but the idea should be that there is a merge request for every algorithm.
• Code that is used in multiple problems should reside in {LIBRARY}_UTILS unless that particular code is very large. In that case we will have to see what we do.

[Mathemalsky]

Is {LIBRARY}_UTILS a single file or a folder?

How to start the project? I think at first we need a CMakeLists.txt or maybe even a tree of such files. Will you create them?

[MilchRatchet]

{LIBRARY}_UTILS is a single file.

Yeah we need a CMakeLists.txt, we could either have one or we could split it up for each library. I think simply having one CMakeLists.txt is fine though. If you want you can create it.

[Mathemalsky]

Ok I'll create such CMakeLists.txt but I want to create one separated file for each folder because then we could easily use the modularity if the project.