[LyX as a competetive coding environment]
> I don't know if that's ever really going to happen, though. It doesn't
> make much sense to add this kind of capability to LyX. The focus of
> LyX should always be on being a great document preparation system, not
> a coding editor.
I agree that LyX is
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Kayvan> On the other hand, I think that the whole thing would be even
Kayvan> clearer (and more complete and up to date) if you wrote the
Kayvan> code and documentation together in a literate style. Each
Kayvan> documentation ch
> 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
pla
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> Super!
Asger> You seem to have found it, and has proven yourself worthy of praise ;-)
:-)
Asger> I think the real problem is that operator != is not well
Asger> defined for BufferIterator. So, the correct (i.e. effici
On Wed, 12 May 1999, Asger K. Alstrup Nielsen wrote:
> P.S. Dia is a good tool, but it's still far from Visio. Is development
> fast?
Lately it has not changed but usually it's fast. BTW some weeks ago I
played a bit with Visio 5 in my brother's notebook. I found that Dia is
much more complet
> I did it yesterday but I have not time to answer right now. I'll only tell
> you that now seems to be much more clearer your idea, with the diagrams.
> It was a good idea to make them (the class diagrams not exactly follow the
> UML notation, thought that's not an impediment to understand them.
On Wed, 12 May 1999, Asger K. Alstrup Nielsen wrote:
> Did you read the documentation/code? Any comments?
I did it yesterday but I have not time to answer right now. I'll only tell
you that now seems to be much more clearer your idea, with the diagrams.
It was a good idea to make them (the cla
> I believe this fixes the segfault.
>
> I can't tell you if the output is what you expect, though.
>
> --- BufferIterator.cpp~ Mon May 10 10:47:10 1999
> +++ BufferIterator.cppTue May 11 11:58:34 1999
> @@ -89,7 +89,7 @@
> ostream & operator<<(ostream & o, BufferIterator const &
I believe this fixes the segfault.
I can't tell you if the output is what you expect, though.
--- BufferIterator.cpp~ Mon May 10 10:47:10 1999
+++ BufferIterator.cpp Tue May 11 11:58:34 1999
@@ -89,7 +89,7 @@
ostream & operator<<(ostream & o, BufferIterator const & b) {
o << "BufferIterat
