On Tue, 2 Apr 2002, Angus Leeming wrote: [...] > static bool build_name (string&,const vector<string,allocator<void> >&); > --------------------------^ > cxx: Error: /usr/include/cxx/locimpl, line 309: #266 "string" is ambiguous > > etc. > > Any ideas?
I suppose your compiler is seeing a choice of std::string and lyxstring (exported via typedef as string). So the question is why? Does `cc -E` provide any insights? In particular, why isn't the "#define __STRING__" sufficient to stop <string> being loaded by some other header? Dumb STL implementation? Don't worry about Lars' desire to ditch lyxstring at every opportunity. It is very useful (and small and assertive and makes compile times more bearable) and the one I always use. Allan. (ARRae)
