The code has been released under an MIT license here: https://github.com/bbcmicrobit...
A story-so-far write up by one of the developers is here: http://ntoll.org/article/story...
Background noise and effects could be added , but it's uncommon enough at the moment that I doubt the robot calls would be able to cope with it even when the spoken voice clear.
I still find myself using printed copies purely because I can *much* more easily flip between pages, and can organise the pages on the desk the way I like as I try to follow the argument (and a self printed copy is better than a bound copy here, because the binding restricts the layouts).
I use a ebook reader/printed copies rather than the screen to give my eyes a rest, and a change. The point is that a single format is not the best for every use, so I think the death of the printed book is overhyped and it will just become another media format (and probably a niche one). But books do have some major advantages over the other formats. They don't require any support technology to read, they are stable for a long time , are not as fragile as an ebook screen, and they are cheaper than an ebook reader. All of which may be important to your needs.
Novels, I prefer in ePub/Mobi formats since the reader I have is has a form factor which allows it to fit into a pocket better than the massmarket paperback format. And this is depsite having a screen approximately equal to the pages size, the ebooks thinner form factor work better given the way most pockets are constructed.
It deals with these issues. And is an enjoyable read anyway - as you'd expect from Stross.
There is no reason for the OOXML specification to use date formats based on the old
Microsoft have specified a new on-disk representation which continues to have a madness just to simplify their load/save implementation. The fact that it is due to compatibility with an ancient bug from a competitor is completely irrelevant. They could have specified the OOXML standard to be clean and dealt with any issues in their save/load code, or elsewhere in excel.
The different impedance is sometime enough to trip the collision detection circuitry. Also the drivers are actually low impedance as they deliberately drive current into the cable , and have high impedance detectors.
It's all about the collision detecttion..., I have seen it work though - but you've got to be careful or lucky.
Except that doesn't account for having a method (destructor) which will be called when your variable goes out of scope.
Then you have generic's on top of that.
And in c++0x, auto, lambda and rvalue refs. There a whole lot more to c++ than objects.
[Note: I program in both. & python & perl &......]
What did you investigate? What samba tuning parameters did you try?
Last year I had a very similiar problem, which actullay turned out to be network card driver issue. I upgraded from the stock debian stable kernel to one from testing and the problem went away.
My point is a single example without actually knowing what was investigated - is just a worthless anecdote.
Make sure your code does nothing gracefully.