[interfacekit] Re: BString

Ingo Weinhold wrote:
> On 16 Sep 2002 burton666@xxxxxxxxxxx wrote:
>>Mh, let's try again, since the other message got messed up:
> 
> Erik, Axel mentioned, that it may be a configuration with the FreeLists 
> list, more precisely something that can be configured by the list owner.
> What obviously happens, is that the list server simply ignores the mails' 
> content encoding field and replaces it by `7bit'. For `quoted-printable'
> the result looks relatively harmless (cf. my early mails to the list), but
> `base64' ends up completely unreadable. 

I'll see what I can do about this.

>>Yeah, sorry, my fault.
>>I prefer to put my code into the CVS even if it's not full tested, since thus 
>>the code is there, and if my hd crashes I do not lose anything.
>>If you prefer, I can go the other way round, keep the code locally until I've 
>>tested it completely.
> 
> No, that's not what I meant. Check it in, but just don't add it to the
> library, i.e. don't commit the Jamfile/support.src, unless you are
> faithful that the code works well.

Fully agreed with Ingo here.  Yes, put *everything* in CVS; there has 
been far too much tendancy to "keep the code locally", which has 
occasionally resulted in the loss of a lot of folks' hard work. =\  Just 
keep it out of the build until it's really ready.

>>Yeah, tests. I really need to write unit tests for BString. The problem
>>is that I really can't understand why support tests don't compile for me
>>(or is it a known problem?). If those tests compiled, I could just add
>>mine and test if they work.
> 
> Mmh, strange, I haven't tried to compile the support tests for a while,
> but IIRC I had no problems last time I did. I will have a look at it in
> the evening.

I will also look into this.  Let's keep this dialog running until the 
issue is solved for everybody.

e

Other related posts: