ruby: fix the most obvious warnings reported while running the tests
ruby: make ConversionToMismatchedType#pretty_print report the field offsets

The most common occurence of mismatching types is differing layout, so...
ruby: allow setting or adding multiple metadata values in one call
metadata: allow empty value sets

So far, one could not make the difference betweeen a metadata key
set to empty and an unset one. This is problematic in e.g. orogen
where we have cases where the include list is empty (but is known
to be empty), as e.g. for /double.

This commit allows to make the difference, as well as to set a
metadata key to empty. It does not change the behaviour of existing
code as the new behaviour is dependent on
ruby: fix documentation
Merge pull request #19 from orocos-toolchain/minor_changes

Minor changes
ruby: fix chaining calls to ContainerType#<<

Doing

  vector << 0 << 1

was resulting in a single-element vector (!)
ruby: fix ContainerType::StdVector#raw_memcpy

The method was looking at the vector type instead of the element type
to decide whether the memcpy was allowed at all.
ruby: validate the provided size in ContainerType::StdVector#raw_memcpy
ruby: fix documentation of ContainerType::StdVector#raw_memcpy
ruby: improve error reporting of ContainerType::StdVector.raw_memcpy
test,ruby: #raw_memcpy is part of StdVector, not ContainerType, reorganize the tests
Removed old dependencies from package.xml

nokogiri and libxslt were removed from manifest.xml in 62838c1ac35f99a105ab32979801a637a6abd4eb.
Merge pull request #24 from meyerj/manifest-cleanup

Removed old dependencies from package.xml
Merge pull request #22 from orocos-toolchain/fix_to_raw_mempcy

fix raw mempcy (fixes #21)
verify that the string element type exists

This fixes a SEGV if the detected string element type does not exist
Merge pull request #25 from orocos-toolchain/fix_segv_on_nonexistent_string_element_type

verify that the string element type exists
[lang/tlb/import.cc] better error-message on import error

did try to "load" a non-existing file and got no clear error message.

still not nice... the read-file-and-pass-content-as-stream hack causes
using the empty string "" as source-id ... which will break all later
error-messages

maybe add "source_id" as fourth parameter to "Importer::load()" with
empty default value? would have to change all load() implementations...

Signed-off-by: Martin Zenzes <martin.zenzes@dfki.de>
[ruby/typelib.rb] use RuntimeError instead of "InternalError"

I assume "InternalError" was defined once upon a time. Its not anymore.
But oroGen knows an exception like this, maybe they are related? well,
crashing while crashing does not look very elegant. so limit the code to
just crash once.

see https://github.com/orocos-toolchain/orogen/blob/298c9dc70880af3afb6925f7d55c5fb414771b6e/lib/orogen/base.rb#L71

Signed-off-by: Martin Zenzes <martin.zenzes@dfki.de>
[lang/csupport/containers] Container-factory: throw "BadCategory" to prevent bad-casts

happens if someone wants to create a container with a name of a type which is already in the database...

Signed-off-by: Martin Zenzes <martin.zenzes@dfki.de>