call #apply_changes_from_converted_types before calculating the byte array (closes #349)
fix memory leak in ValueOps::load

load() was calling init() on all included containers, but was actually given
already initialized containers. This did not show up in the Ruby bindings as we
create a new object and pass it to load() (which meant that we erased an already
empty std::vector, which does not leak anything). However, when given an already
initialized non-empty object, it would indeed reinitialize the vector thus
leaking the already allocated memory.
ruby: pretty-print /std/string as a string
ruby: fix access to nil @exported_templates in #find_exported_templates
ruby: make from_ruby call apply_changes_from_converted_types on the returned value

It is assumed that the value returned by from_ruby can be used
as a typelib value, i.e. directly on a C++ interface. However,
if apply_changes_from_converted_types does not get called, the
underlying C++ structure is not up-to-date (and therefore the
assumption is broken)
ruby: do not override custom convertions to/from Hash and Array by the default ones
ruby: fix source code line for struct/class/enum

GCCXML reports the line of the opening bracket ({) while we really
would like the definition line (struct/class/enum)
Merge remote-tracking branch 'autobuild/master' into next

Conflicts:
	test/ruby/test_typelib_gccxml.rb