Hi - >Hi. I'm working on a Cryptography module for Chapel based on OpenSSL. >I have prepared a CHIP regarding this and would appreciate your feedback >during this process. >The CHIP also includes a demo(still to be refactored) to give an idea of >how the current approach is being taken.
This CHIP looks pretty good to me. I have just a few things to bring up. First, do you expect that Crypto.chpl will support other cryptography libraries / implementations? You might construct a different API if you envision that OpenSSL is the long-term dependency for this module than if you were expecting another library (or a totally native Chapel one) to be optionally swapped in in the future. Second, once you have a sense what the Crypto.chpl API will look like (what types, functions, documentation) I think it would be a good idea to separately request feedback on that. Lastly, the document says: > Using extern blocks was the next logical step as writing C functions for > OpenSSL is easy and debugging is also not an issue due to the immense > help available online. But it reduces the code maintainability. I'm not sure I understand why extern blocks would reduce maintainability. Certainly they can require the callers of the C methods to do more work than if the extern proc is constructed by a person. I don't object to manually writing the `extern proc` declarations going forward; I just don't think it's really about maintainability. Cheers, -michael > > >Thanks. > > >[Link to the CHIP]: >https://github.com/chapel-lang/chapel/blob/master/doc/rst/developer/chips/ >21.rst > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
