- I don't remember anything you wrote about a Pike Nettle interface, but I've not had any major problems with the current one. The current interface, but with Capitalized programs and a move from update/digest to feed/drain would satisfy me.
update/digest is farly standard terminology for hash functions. Your wish is the first for feed/drain. feed/drain would make more sense for things liek a CBC object, I guess.
I think the most fundamental change I'd like to do (trivial renames) is that I'd like algorithms to be represented as objects, with a `()-method, instead of as plain programs.
/ Niels Möller ()
Previous text:
2003-03-11 22:44: Subject: nettle-1.7
Blame on me. I should have gone English. The topic is how-to-replace-Crypto-with-Nettle.
jhs or some pelix root can fix an account for you.
I don't remember anything you wrote about a Pike Nettle interface, but I've not had any major problems with the current one. The current interface, but with Capitalized programs and a move from update/digest to feed/drain would satisfy me.
I agree that not having Nettle in the source tree could be a good idea, if we post enough pointers to where to find it (e.g. putting releases on the Pike ftp). As long as changes can be countered by configure scripts I don't see that there is a problem with incompatible changes in Nettle.
/ Martin Nilsson (har bott i google)