Thanks for adding the BINARY IsoType. It is exactly what I needed. Can you add a DATE10 that would have the format of MMddHHmmss? I can contribute the code, if needed.
I don't think that's really part of the ISO spec, I've never seen it, and while I don't have the latest spec directly from iso.org, wikipedia doesn't mention anything like it either: http://en.wikipedia.org/wiki/ISO_8583#Data_elements
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a client that uses data element 13 in a non-standard format. Instead of using MMDD, the client uses AAAAMMDD. Someone else may also have need of this type and I am willing to contribute the code. If you would rather keep this library as strictly standards compliant, I can code around this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry I made a mistake the MMddHHmmss is already implemented as DATE10. I need a DATE8 with the format of yyyyMMdd. Thanks
I don't think that's really part of the ISO spec, I've never seen it, and while I don't have the latest spec directly from iso.org, wikipedia doesn't mention anything like it either: http://en.wikipedia.org/wiki/ISO_8583#Data_elements
I have a client that uses data element 13 in a non-standard format. Instead of using MMDD, the client uses AAAAMMDD. Someone else may also have need of this type and I am willing to contribute the code. If you would rather keep this library as strictly standards compliant, I can code around this issue.