Skip to content

Conversation

@taa01776
Copy link
Contributor

@taa01776 taa01776 commented Aug 9, 2018

…et enums, string names, and messages.
Also changed the harness code for registering nonfatal errors to use this. It's kind of an ugly include file hack, but it works to define the enum, an array containing the error names ("JANICE_OUT_OF_MEMORY"), and another array containing the error strings with only one entry of the actual error information.

Not strictly necessary, but I think it makes the error definitions cleaner.

@taa01776
Copy link
Contributor Author

I notice the shorter-error-list pull request is still pending.
This might also be controversial, but I ran into a number of problems using the JanICE test harness executables, because they construct file names by concatenating strings in a fairly naive way: failed, for example, when I supplied absolute path names for images in a detection protocol file. I changed them to use boost::filesystem primitives to construct new path names instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant