If it actually worried about noticing and reporting dupes, I'd leave it with its own copy of the code, but as it stands it was just an incomplete copy & paste of the other. Now it gains parseEnumArray's understanding of empty strings.
…ver. Cache the result.
This class could really use some cleanup
Catching an error in this function is irritating when using a debugger - the callstack where the error originated is unwound when the error is caught (obviously), so you can get a stacktrace string, but you can't actually inspect the stack with the debugger.