Platform independence

From CSP

The goal is to build and run cleanly on both Windows and GNU/Linux. Since most of the CSP developers work almost exclusively on just one of these platforms, changes that are likely to be platform sensitive should be tested by at least one other developer "on the other side of the fence".

True platform-specific issues are fairly rare now. The most common problems are compilation errors due to differences between GCC and MSVC. For example, it is easy to forget to add the CSPSIM_EXPORT macros to class and function declarations when developing on GNU/Linux, since GCC does not need these qualifiers. This type of error is relatively easy to fix once it is apparent, so it is often expedient to just submit code once it compiles on your platform. Developers on the other platform should test new submissions as early as possible and correct any minor compilation errors.