"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| Am I wrong, that the ANSI C++ library is on very few systems (namely
| sgi) available as a manually optimized and thoroughly debugged option?
Yes, I believe you are wrong.
AFAIK all major compiler vendors have released new versions of their
products since the ANSI C++ standard was ratified.
Using the Standard Library should not be a problem. (even for gcc
2.7.2 it is failry usable.)
| You should also report, which compilers are 'LyX proof' and test for
| the compiler/version in the configure process, warn users about
| untested:
This we can do.
| - My idea here is to restrict messages so as to simply print to a log
| file/named pipe with a tag that identifies and classifies the message
| using only standardized functions. The respective gui wizard would then
| decide how and if the message be presented to the user.
|
| Popups are still an obstacle for splitting the code into independent
| libraries (using only posix functions) and linking as shared objects.
| Then you would have a separate dynamic library providing the necessary
| non-standard OS and toolkit interface.
I am not sure how fond I am of the idea of creating a bunch of
libraries. Why do we need it? OS/2 can have them if wanted, but on
UNIX it will make the installation process harder and more errorprone.
| - Defining strict and simple inter-library interfaces providing
| abstract data types and simple functions as well as starting to
We are not interestet in inter-library interfaces, but in inter-module
interfaces. We care ding about libraries.
| If I understood forms home page correctly, 0.89 is not a production
| release, yet a 'for evaluation only' version, released for a fraction
| of the supported systems. For non-experimental use they still only
| support 0.88.
Perhaps we will support 0.88 until 0.90 is released then.
Lgb
