Hmm. I think I need a visual of what’s going on. A map. Working on a diagram. At work, so I might not have anything until later.
@David_Keeney Do you think a test/prototype project would be a good idea? C+±only. Copy/paste a couple classes from nupic.core. Pick two languages for binding. Keep the same/similar project structure. Test it without having to support legacy, on Windows, Linux, and OS X? No python anything. The core extraction plan describes it’s goal to be C++ only, so I too was surprised to find a dependency on python. That plan describes:
nupic.core - C++
nupic-<flavor> - language binding
nupic-<flavor>-client - language client
As an alternative, maybe:
nupic.core
nupic.bindings - shared binding module? necessary?
nupic.bindings.<flavor>
nupic.<flavor>
Then we can have that to discuss and maybe see if we can do anything for master?
@rhyolight Maybe a new topic, once we get things ironed out? See what we need to do. Not sure this could be merged into master, due to its current state and the impact of this work.