Closed nununo closed 5 years ago
Implemented a simplified but practical approach:
FIELDNAME accepts multiple fieldnames separated by space. When more than one is found, the same quantity of values is expected and no range is allowed (checks are already in place for this according to #32).
Unit tests are missing for _DATA.
What if we want to create constants which are comprised of more than one field? Like:
Currently abaK's API always focus on a single field. Which is the most common scenario and thus should remain the its main focus.
But... would it be possible to extend abaK's functionality to accomplish this without destroying its simplicity and clarity?