Changed Paths:
    Modify    /trunk/include/chaiscript/dispatchkit/dispatchkit.hpp
    Add    /trunk/src/memory_leak_test.cpp

Add sync_cache to set_state code to fix logic flaw in resetting of state and memory leak. #92

Changed Paths:
    Add    /trunk/unittests/memberscope.chai
    Add    /trunk/unittests/memberscope.txt

Testing of memberscope so we can close #91

Changed Paths:
    Modify    /trunk/include/chaiscript/language/chaiscript_eval.hpp
    Delete    /trunk/unittests/method_lambda.chai
    Delete    /trunk/unittests/method_lambda.txt

No longer allow a local variable to be used as a function during dot notation sugar lookup. It's far less confusing this way

Changed Paths:
    Add    /tags/release_2_3_2 (from /trunk :480)

Tag r480 as release 2.3.2

Changed Paths:
    Modify    /trunk/include/chaiscript/chaiscript_threading.hpp

Convert from #warning to #pragma message for notification of thread safety being disabled, so support more compilers portably

Changed Paths:
    Modify    /trunk/include/chaiscript/language/chaiscript_eval.hpp

Fix empty array unit test by reimplementing the node->children.size() test erroneously removed in r466

Changed Paths:
    Modify    /trunk/include/chaiscript/language/chaiscript_eval.hpp

Fix empty array unit test by reimplementing the node->children.size() test erroneously removed in r466

Changed Paths:
    Add    /trunk/unittests/vector_push_empty.txt

Add the answer to the unittest I added earlier

Changed Paths:
    Add    /trunk/unittests/vector_push_empty.txt

Add the answer to the unittest I added earlier

Changed Paths:
    Add    /trunk/unittests/vector_push_empty.chai

Add unit test that dies after r465

Changed Paths:
    Add    /trunk/unittests/vector_push_empty.chai

Add unit test that dies after r465

Changed Paths:
    Modify    /trunk/include/chaiscript/dispatchkit/bind_first.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/function_call_detail.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/proxy_constructors.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/proxy_functions_detail.hpp

Clean up leaking #define's for iterations (n, m) that could mess up subsequently included files such as boost/signals2.hpp

Changed Paths:
    Modify    /trunk/include/chaiscript/dispatchkit/bind_first.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/function_call_detail.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/proxy_constructors.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/proxy_functions_detail.hpp

Clean up leaking #define's for iterations (n, m) that could mess up subsequently included files such as boost/signals2.hpp

Changed Paths:
    Modify    /trunk/include/chaiscript/dispatchkit/boxed_value.hpp

Remove std::swap implementation that was not supported for multiple file compilation.

Changed Paths:
    Modify    /trunk/include/chaiscript/dispatchkit/boxed_value.hpp

Remove std::swap implementation that was not supported for multiple file compilation.

Changed Paths:
    Modify    /trunk/src/example.cpp

Minor fixes to example.cpp to avoid exceptions

Changed Paths:
    Modify    /trunk/src/example.cpp

Minor fixes to example.cpp to avoid exceptions

Changed Paths:
    Add    /tags/release_2_3_1 (from /trunk :469)

Retroactively tag release 2.3.1 as r469

Changed Paths:
    Add    /tags/release_2_3_1 (from /trunk :469)

Retroactively tag release 2.3.1 as r469

Changed Paths:
    Modify    /trunk/include/chaiscript/dispatchkit/bind_first.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/bootstrap_stl.hpp
    Modify    /trunk/include/chaiscript/dispatchkit/register_function.hpp

Get compiling with Visual Studio 10 beta 2. Had to work around issues with conflicts between boost::function and VisualStudio's std::tr1::mem_fn (http://so cial.msdn.microsoft.com/Forums/en/vcprerelease/thread/e04d93ed-d686-4ef6-9939-26 e34c0955eb). Also had to work around non-standard overloaded std member functions in std::map (http://msdn.microsoft.com/en- us/library/fe72hft9(VS.100).aspx) Strongly consider rolling this back when the issues are resolved between microsoft and boost. Also, needs to be tested across all platforms.