strappy_directory_structure

Redesigning the Strappy code base architecture.

To facilitate development of code that implements the core program induction algorithms while simultaneously using this code to run experiments in various domains. It would be best if the code bases for these uses was as distinct as possible. Also, we want to relate publication related stuff to the code that supports it. I propose the following structure:

• core
• strappy-core.cabal
• src/
  • Strappy
    • Core
      • EC
      • Analysis
      • Utils
      • etc... (other supporting code).
• projects (directories for individual projects)
• morphology (a publication specific directory)
• strappy-morphology.cabal (a separate cabal library for this project)
• drafts/
• bib/
• tex/
• src/
• number
• etc...