Dixitur illum ih8mj@fjf.gnu.de scribere...
For such a unit, I'll give permission to include my code from the interface (in fact, I'd ask for using the same interface for compatibility) and the implementation of my new routines `MD5File' .. `MD5Compose'.
(And, BTW, if you want it included in the GPC distribution, please note the GPC Coding Standards. If I'd have to reformat the code or do other significant work with it, I won't do it, see above. Also, please don't change `* $10' to `shl 4' etc., as you did. Write high-level code and leave the low-level optimizations to the compiler.)
Okay, this is now a second try:
- the md5c.c file is public domain, rewritten by the guys at fourmilab.ch (thanks Todd Miller @openbsd for the hint) - the md5.pas file has as few differences as possible to your code, so (I hope) coding styles are not an issue. (I'll read the standards anyways) - endianness isn't an issue either - if BYTE_ORDER or LITTLE_ENDIAN are not defined, it might still work (unless the preprocessor doesn't play with us), it's just (a bit) slower on i386 then.
I pledge for this being included into GPC.
cu, //Thorsten