On Friday, 21 September 2012 at 09:50:06 UTC, Jacob Carlborg
wrote:
On 2012-09-21 10:56, Chris wrote:
Thanks, that's cool. I really need something like that,
because I still
use a lot of features that are deprecated by now and are all
over the
place. The reason for this is that my project developed so
fast and grew
so big in a short period of time (D speeds up development)
that it is
hard to trace down all deprecated methods and replace them.
Also, the
library seems to be changing all the time anyway, so who knows
whether
or not the new methods will be deprecated again in a few
months' time.
But as the days are getting shorter I might find the time to
skim
through the code and finally do the dirty work I keep putting
off.
That's been a quite annoying problem of D. But things have
settle down quite a lot in recent times. Hopefully there
shouldn't be that much breaking code these days. But if you're
relaying on a bug that was fixed it will still break your code.
Yeah, I see. I didn't realize it was a fixed bug, because I had
checked process.d online and thought "Well, it should work". It
didn't occur to me that the environ-thing for Mac OS X wasn't
included in older versions. But I'll know better the next time!
I hope you are right and things have settled down now, because I
would really like to keep on using D and see it take off someday.
I have been able to easily integrate my D code into Python, C,
Lua (and now hopefully Java) programs and access C libraries
easily from D, which - apart from all the nice features the
language has to offer - is a real big plus. The only drawback is
the lack of a fully-fledged cross-platform GUI, but that's a
different story ...
