From: René J. <rvj...@xs...> - 2021-08-18 13:41:14
|
Hi Jeff, How are you? Just found out about a corner case in Pipelines for NetRexx - I was implementing DIGEST and in an effort to be CMS compatible I noticed that the hash is not returned in hex on CMS, but as bytes, which you can later translate. Not being able to get the same hashes, I noticed that I needed an XLATE E2A before the DIGEST stage, and then still it would not work. So dumping every stage with SPECS 1-* C2X 1 I noticed that CMS Pipelines has an extra space in the pipeline, unless I put the pipe separator litterally at the end of the string. And lo and behold, in the source for the LITERAL stage it actually tells us (Ed does) that CMS does preserve trailing spaces, and njpipes does not. What do you think, do we need to fix this? And also, Do we want to have DIGEST output bytes instead of hex? I am leaning to ‘yes’ on both counts, but I would like to hear what you think, and whether fixing LITERAL will break anything. Other thing, do you think you can present at the symposium, when that is online and somewhere in October? Best regards. René. |