You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason for taking this approach would be that the dachar library would exist as a stand-alone component that was entirely independent of any implementation of fixes.
Benefits of this approach would be:
Any external tools using the information generated by dachar could use the fix definitions.
dachar does not hard-code specific implementations.
Drawbacks of this approach would be:
An extra language/encoding of the fixes is required - this must be written by the project. (There might be existing standards/approaches we could use).
Our daops library will need to define mappings from the language-agnostic form to our own daops functions.
Description
We have created fixes that are specific to our
daops
library, e.g.:An alternative would be to define all fixes in a language-agnostic form, such as:
The reason for taking this approach would be that the
dachar
library would exist as a stand-alone component that was entirely independent of any implementation of fixes.Benefits of this approach would be:
dachar
could use the fix definitions.dachar
does not hard-code specific implementations.Drawbacks of this approach would be:
daops
library will need to define mappings from the language-agnostic form to our owndaops
functions.@cehbrecht and @huard: what are your thoughts on this issue?
The text was updated successfully, but these errors were encountered: