Additional memory leaks

[palemieux]

def_copy not freed if addition to dictionary fails at

regxmllib/regxmllib/src/main/cpp/com/sandflow/smpte/regxml/dict/MetaDictionary.cpp

Line 87 in 9378fb5

if (_visit(def_copy)) {

def_copy not freed if addition to dictionary fails at

regxmllib/regxmllib/src/main/cpp/com/sandflow/smpte/regxml/dict/MetaDictionary.cpp

Line 107 in 9378fb5

if (_visit(def_copy)) {

def_copy allocated but never used at

regxmllib/regxmllib/src/main/cpp/com/sandflow/smpte/regxml/dict/MetaDictionary.cpp

Line 121 in 9378fb5

Definition *def_copy = new PropertyAliasDefinition(def);

ft and parser never deleted at MetaDictionaryTest.cpp

[ErikCJohansson]

I searched for 'new ' to take a look at any additional allocations. I see that the pattern 'throw new' is used in several places. I believe this is a mistake as it will throw a pointer to a dynamically allocated object, which will leak unless there is a corresponding 'catch' with the correct type that calls 'delete' on the thrown object.

[palemieux]

throw new

Ah. Good catch. Leftover from Java conversion.