It is a fairly old application but deprecation should be easy, just leave the old stuff hanging around if you are not going to use any of it and then blast it in 90 days. A couple of other comments:
1. You should not create a module called ecrypto because it has nothing to do with the application name. Perhaps crytographic would be a better name. Any other modules should obey the prefixing rules. 2. On the math module. When going through and building this it seemed as though there were a number of functions that were generic just math and not really crypto specific, that is why I separated them out. They could eventually move into erlware commons. As you can see I never did that though so take that with a grain of salt. On Sun, Feb 6, 2011 at 10:05 AM, Jordan Wilberding <[email protected]> wrote: > I am probably going to make changes to the cryptographic API. > There are 2 things I want to do. First, I want to completely remove the > padded encrypt and padded decrypt for now. Second, I want to rename cg_rsa > and cg_math into one single module called ecrypto or something like that. > Do people think we should go through the whole deprecation process, or is > this library young enough we can just do a wholesale transformation at this > point? > Thanks! > JW > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > -- Martin Logan Erlang & OTP in Action (Manning) http://manning.com/logan http://twitter.com/martinjlogan http://erlware.org -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
