> > As mi_info_threads is now not mi specific, should it be called something > > like info_threads_1? > > The "_1" is a bit misleading, as the function can print information about all > threads just fine. How about "print_thread_info"? Sure. You don't really need to ask now. -- Nick http://www.inet.net.nz/~nickrob