[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: urlstring testing/enhancement
From: |
Federico Montesino Pouzols |
Subject: |
Re: urlstring testing/enhancement |
Date: |
Thu, 9 Jan 2003 11:53:49 +0100 |
User-agent: |
Mutt/1.4i |
Hi, ...
On Mon, Jan 06, 2003 at 04:45:04PM -0800, Chad Yates wrote:
> I built urlstring testcases this weekend. Here are the test cases performed:
> URLStringTest.testBinaryBase64EncodeDecode ...
> URLStringTest.testStringVersion ...
> URLStringTest.testTypicalUrlEncodeDecode ...
> URLStringTest.testTypicalTextBase64EncodeDecode ...
> URLStringTest.testSimpleTextBase64EncodeDecode ...
> URLStringTest.testComplexTextBase64EncodeDecode ...
> URLStringTest.testPaddingPerfect ...
> URLStringTest.testPadding1Short ...
> URLStringTest.testPadding2Short ...
>
> I also added Base64 functions that take std::string arguments for the encode
> output and the decode input. I don't know where the line is supposed to be
> relating to string usage as I see most of common c++ is char* based, but
> there seems to be std::string usage in some classes. personally I like
> having it as an overload option. I can post diffs showing the new functions
> if they are wanted.
>
I think we should include these new functions. For the last
months some things have been changed and updated to progresively
incorporate string as preferred to char*. These new functions do not
break backwards compatibility, so I see no reason to not include it.
> ,Chad
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp