> While you're doing that, is there anything to stop you from moving the > non-inline function definitions into a separate .tcc file in > anticipation of some future implementation of the export keyword, or > is that a bad idea? Good idea! It would also match string, io, and locales. -benjamin