Re: ost::Digest class Re: protected initDigest() method

[Federico Montesino Pouzols]

        Ok, the change is done in CVS for both 1.0.14 and testing.

On Sat, Nov 29, 2003 at 10:23:27AM -0500, David Sugar wrote:
> Yes, it was originally meant as a method to be used in other derived
> classes.  But I see no issues with changing it either, so long as any
> changes like this one are also tracked in the "testing" branch.
> 
> David
> 
> Federico Montesino Pouzols said:
> >
> >     Hi,
> >
> > On Wed, Nov 26, 2003 at 03:22:55PM -0500, address@hidden
> > wrote:
> >> The ost::MD5Digest/ost::SHA1Digest/ost::SHA256Digest classes all
> >> inherit  from the abstract ost::Digest class.daThe ost::Digest class
> >> lists a  protected abstract method, initDigest().daThe digest classes
> >> that inherit  from ost::Digest make their initDigest() methods
> >> public.daI want to use the  ost::Digest class as an interface to
> >> multiple digests.  That way I can have  a function that takes a
> >> ost::Digest* and uses it for it's digest computing  needs.
> >
> >     It seems that initDigest was originally intended to be used
> > only internally by derived classes, but I think the idea you propose is
> > quite interesting. I see no reason why initDigest cannot be public.
> > Should we make it public?
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> 
> 
>