Jebbs
Adding more D to the mix?
As I've been learning more of the D standard library, I've been finding many very useful bits of functionality. For example, the time capabilities in std.time.
This leads me to wonder if it would be a good idea to try and incorporate more of the standard library into DSFML, instead of having to rely on DSFML-C as much (in this case for the clock).
I understand that keeping similarities to SFML is a good thing, but I also feel that trying to rely less on external libraries could be beneficial. @Jebbs What are your thoughts on this?
Personally, I'd strongly prefer DSFML to rely on the standard library when it can. That's what the standard library is there for, after all.
My thoughts exactly. Perhaps trying to find more places to look for converting than simply the Time/Clock modules is a decent step.
Hey guys,
Sorry about the delay. I was out of town for the weekend.
Anyways, I have mixed feelings about this. I mean, I do use the standard library sometimes, but I try to not use it as much as possible because it is such a huge dependency that can import other modules without you knowing, or allocate with out you realizing.
If you can make a really good argument, then I will move forward with this. Otherwise, I just don't see a lot of benefit. I barely have time to work on the library as it is, and this could potentially be a huge undertaking that takes time away from something that could in my eyes be more beneficial to DSFML.
It is a binding after all. It is supposed to rely on DSFML-C. :P
