The company I work for hired/cooperated with two other companies on some code for an embedded system. One company coded the operating system, and the other coded a driver that is used by the operating system. Due to FAA requirements, the code must be in C - no features from C++ are allowed. It is now our task to get the driver integrated with the operating system and get applications running on all of it. I don't know what kind of programmers the other companies employed, though - there are functions, structures, and global variables with single character names. Among other name conflicts, the operating system defines a function s(), and the driver has a structure s. These two things appear in thousands of lines of code, and it must all be compiled together to work. They are never both used in the same file, however. Is there some incredibly clever way of avoiding this conflict without spending what could literally be days inserting descriptive variable names in place of 's' and the like? In C++, I'd rely on some combination of namespaces and function overloading to make up for others bad coding practices, but I don't have that liberty this time.