-
Updates to the c API to handle returning strings more safely
-
… use *args for the rest in python)
-
Instead of returning references to static memory (which are invalidated by subsequent or concurrent calls to the function), require users to input string buffers to functions that return strings. Affected functions: br_get_filename br_get_metadata_string br_scratch_path br_objects br_most_recent_message In some GUI functions, use C++ functions instead of going through the c api add a c++ method correspondign to br_objects (which returns a stringlist instead of merging the lines) br_read_pipe and br_get_header also use static memory in a similar way, but are not addressed in this commit.
-
br_about, br_version, and br_sdk_path return pointers to static memory declared at function scope, that is intialized once and never changed. In versions of visual studio (prior to 2013 apparently), this initialization is not thread safe (thread safety of this operation is in c++-11). Removed references to managed_return_value in the documentation of these methods. The memory returned here is not invalidated by subsequent calls to the function, so that comment does not apply.
-
…-gui is specified as the first argument
