I haven’t been able to work on Fhtagn! a lot recently… paid work keeps interrupting1. In the meantime, faithful cultists might find that the waiting is a little less dreadful they watch the video below:
If you are a non-commercial user, e.g. if you use this software for personal, educational or other non-profit use, all that changes for you is that you now must publish the source code to any changes you make to this software, provided you distribute these changes in some way.
And it’s done! I’ve just tagged 0.2.0 aka Black Brotherhood, the first release of Fhtagn! that can reasonably be called a release.
People following this project will note that a number of issues that used to be associated with 0.2.0 got pushed to 0.3.0 in recent weeks. I just felt that I’d rather postpone individual features than keep putting off a release.
Please note that windows is still not officially supported. One of the items on the TODO-list for the next release is to improve on that.
A while ago, I sat down to write a few allocators for C++ objects and/or STL containers. That is, inspired by an article on STL-compatible allocators, I sat down to write one such allocator, but made it possible to feed it memory from a variety of what I chose to call pools. One such pool I modelled after what I dimly recall having read in the code of Python‘s allocator.
You can find all of that effort in the memory sub-directory in fhtagn!’s trunk — but more important than code, right now, is another question: why should I be interested?
I admit it, I’m lurking on the boost developer mailing list. Most of what’s sent there goes past me, I don’t really feel I have the time to read it all. And sometimes I even post drivel there, usually only to be reminded that I hadn’t paid attention to detail. Such is my lot.
But there was a recent bit of activity on the mailing list that I wanted to share with you, because it was about a constrained value library about to be submitted for review. In the boost world, new libraries are submitted for review, and the results of the review determine whether or not the library is included.
In case you hadn’t noticed, the buildbots, long defunct due to a strange bug, have been fixed. They’re also switched over to SCons builds, so now produce nightly builds again.
I’ve also finally removed the mailing lists from sourceforge.net, making this site here the home of all infrastructure for Fhtagn!. The new development mailing list – the only one for now – is firstname.lastname@example.org. You can find the archives on gmane.org.
We’ve wanted some advaced feature in the Fhtagn! builds, which would have been pretty ugly to hack up in autotools. For that reason, and because it just makes building a bit nicer, we’ve moved trunk over to use SCons.
I’d suggest heading over to the SCons User Guide for a bit of background. The README bundled in trunk includes instructions specific to Fhtagn! But if you’re impatient, building Fhtagn! shouldn’t really be a lot more effort than running scons on the command line.