[uwe]

Hi Kris,

during my work on the UTF converters i discovered a bug in your converter (basically because i copied it and modified then :) ). In the UTF-16 to UTF-8 converter you have to replace 0x8000 by 0x0800 (that value is the first to be encoded in 3 bytes).

Ciao
uwe

[kris]

[teqdruid]

[kris]

Why didn't you say so before?

It's really just been a case of priority, and I've been waiting for Ben too! I want to keep the options open though, and perhaps Indigo has something nice that we can adopt, or merge with?

[teqdruid]

I don't really care where it comes from, but I need a good Containers API with a good class hierarchy. If it's in Mango, all the easier for me, plus it'll probably have the same great hierarchy that the rest of Mango has.

I have't looked at either Indigo, or DTL (which I doubt even compiles at this point) but the little I've seen of MinTL doesn't make me think that it would be a good candidate for inclusion in Mango- unless Ben is making some pretty radical changes.

It seemed more like a C-style API to me. Almost no inheritance, and really boils down to a collection of structs and associated functions. I'm not saying this is a bad thing- I'm betting Ben gets a lot of speed out of it, but it just didn't seem in the Mango style... I'll reserve final judgement until I see some of his latest stuff, however.

I'm hoping it won't take too long. I just finished finals today, so I've now got some free time (famous last words) to get back to work on my project.

I'll take a look at Indigo soon.

[kris]

[uwe]

Sorry i took so long for my answer, i simply forgot to check back :(

I have already discovered the first bug you spoke about. But i am not so sure about the second... The conversion module has passed all unit tests after some debugging, but i'll look into it again, thanks a lot.

I am not sure what you mean with "viral license". Do you mean you can't take something from my code back into your project because you would have to change your license?? Well, no prob, i was not thinking much about licensing issues (all that stuff sometimes annoys me), just taking the "popular" one i know. Can be changed, you can simply take my code, distribute it under your license and write somewhere "uwe helped me" or similar :)

Sure you can use Indigo in Mango. I was dissatisfied about the String class either (that's why i did not write it to perfection), mostly because of the dumb ICU porting that just produces bloat, and was already done by you. I did not want to be dependant on ICU _and_ Mango, that's all. If a string class weren't so damn important for almost any program, i would have abandoned it.

Ciao
uwe

[kris]

[uwe]

As i said, if you need something of the Indigo code (or the utf conversion package), just take it. No need to include the license as well. Something like "other authors: uwe" would be nice. I'm always happy if i can help.

I have already looked at your hashmap, and will perhaps use it as an implementation draft. I do not plan to make Indigo thread-safe in the near future, as the Qt containers are not, too (ok, they are somehow thread-safe, but you cannot access the same container from two threads, just copy it thread-safely). But i will look over Doug Lea's code, thanks for the hint.

By the way, did you need thread-safe containers often in your projects? I never needed one yet, and i program for quite a long time (ok, did not write so much threaded code either). Just once i had a very large and complex data structure that had to be thread-safe, but that was really a more complicated issue than solvable with a thread-safe vector/list/whatever.

Ciao
uwe

[kris]

[uwe]

I looked at Doug Lea's stuff, especially at the containers. But there were no concurrent lists/arrays, just copy-on-write versions, and versions wrapped in synchronizations (which can be easily realized in D by synchronized{} statements where necessary). Thus the Vector and List/LinkedList can stay as they are, String anyways. As the Map is a linked list too, it cannot be made thread-safe as well.

But i will try to do the trick with the Hash, if it does not impact on performance and simplicity too much. As you said, Ben Hinkle ported the stuff already. Much as i would be pleased to see Indigo in Mango, the aim for Indigo is to provide simple but high-performance containers for people that want to write productivity apps in D without understanding the difficult design of yet another template library.

Ciao
uwe

[kris]