OpenCog Framework  Branch: master, revision 6f0b7fc776b08468cf1b74aa9db028f387b4f0c0
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Groups Pages
Todo List
Page cogutil library
link to definitive list of variables (keys)
Member opencog::AtomSpaceBenchmark::showMethods ()
should really encapsulate each test method in a struct or class
Class opencog::HandleSeqIndex
Notice that it this wastes a fair amount of RAM by storing a copy of a HandleSeq — it could save a fair amount of space by storing a pointer to the HandleSeq that is in the Link already (at the cost of some fragility in Link deletion). Alternately, we could use a "HandleSeq cache", analogous to a string cache, to ensure only one copy of a HandleSeq per system... XXX FixMe!
Class opencog::IncomingIndex
The iterator is NOT thread-safe against the insertion or removal of atoms! Either inserting or removing an atom will cause the iterator references to be freed, leading to mystery crashes!
Class opencog::TypeIndex
The iterator is NOT thread-safe against the insertion or removal of atoms! Either inserting or removing an atom will cause the iterator references to be freed, leading to mystery crashes!
Class opencog::UREConfigReader
: It doesn't support the hierarchical configuration structure described in http://wiki.opencog.org/w/URE_Configuration_Format#Rule-Based_System_Hierarchical_Structure, instead it assumes all parameters are duplicated for all systems and subsystems, for now.
Page spatial library

TNick: IMHO this is a mess

TNick: There exists a templated Computational Geometry Algorithms Library who's goal is to provide easy access to efficient and reliable geometric algorithms in the form of a C++ library. Maybe we shall not reinvent the wheel.

if run_tangent_bug is to stay then it should generate output elsewhere