Didier> Hrvoje Niksic <hniksic(a)srce.hr&gt; writes: Didier> BTW, what are exactly the arguments against using C++ code ? Now that the C++ standard is finally done, compiler implementers will not be able to use the moving target of standardization as an excuse to not improve their compilers, as many have done for the last 5 years. Compilers released after the year 2000 or so will at least attempt to implement the same standard language. But in 1998 the differences in implementation are still an issue. A bigger problem is that C++ compilers are just too damn picky. There are standards that have changed slightly over the years, e.g. socklen_t replacing int or unsigned int. It is nice that C gives you warnings for such inconsistencies, while still allowing compilation on a wide variety of systems. Using C++ makes it much harder to create a working executable on a system not used by a regular XEmacs maintainer. The current situation of using the common subset of C and C++ is the best compromise for the next few years. We can rethink using C++ as the primary language for XEmacs the next millenium. Martin (writing from a C++-compiled XEmacs)