Thanks Pete,

I don't think the issue right now is "how" to implement it (because with yours we now seem to have three implementations) but rather "where". But let me get back to "how" anyway. I think the following API would be usefull

@interface NSData (MD5)
- (NSData *)md5Digest; /* This method actually implements the calculations*/

- (NSString *)md5StringUsingEncoding: (NSStringEncoding) enc;
- (NSString *)md5String; /* uses default encoding.*/
@end

@interface NSString (MD5)
- (NSString *)md5StringUsingEncoding: (NSStringEncoding) enc;
- (NSString *)md5String; /* uses default encoding.*/
@end

But more importantly is where these Categories should go:

1. base/Additions
2. gscrypt - well actually I wouldn't change the existing implementation, I would just try handling the pam_-problem transparently with LIBRARY_DEPENDS_UPON or/and configure.
3. some official gnustep-base-extension library to catch alle GNUstep-base features that base doesn't depend upon and could be written to compile agains OS X/4.2.

If this can't be decided today, I'll consider "hacking" them into gsweb directly until we've decided which way to go.

Comments? Manuel?

Cheers,
Dave




_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to