> Asger> !(i == b.path.end()); ++i) {
>
> No, that doesn't work. I tried it. The problem is that i increments
> past b.path.end(), and you segfault in the same place.
Hmm, that surprises me. I think there is a problem with
operator++ then. Anyway, you have pinpointed me to the right
place, and I'll investigate when I have time.
Thanks again.
> I like your diagrams. They make everything much clearer.
>
> On the whole, I found the documentation clear and easy to follow.
>
> On the other hand, I think that the whole thing would be even clearer
> (and more complete and up to date) if you wrote the code and
> documentation together in a literate style. Each documentation chunk
> could be followed by the implementation of the class that is being
> described.
That is a good suggestion, and I can see a lot of good reasons for
this. However, I have the mayor problem that I don't like LyX as
my coding editor. I much prefer GNU Emacs *and* Microsoft Visual Studio 6.
Notice that I use both, on and off, and I can't accept to settle on
literate programming in Emacs alone.
So the problem is this:
We have a LyX document with documentation and code. This is the
most current and up-to-date document, but it's hard to edit the
code.
>From this, we generate residual source files. These are not meant
to be directly editing.
However, I'd like to edit the residual source files directly, because
the best tools for source code editing is not LyX.
So, there are two solutions:
1) I need a way to reintegrate the changes in the source file into the
documentation.
2) LyX is improved to be competetive with Emacs and VS regarding source
code editing.
Either solution is hard to achieve, but I hope that number 2 will be
easier with a new kernel extended with a suitable scripting language.
> You can shoot me now, if you want. :-)
No, you just found a hard-to-find bug for me! I was about to shoot
myself, and probably had if not I had Delta Force ;-)
Greets,
Asger
