#HOW TO WRITE C CODE FROM MIPS PORTABLE#
#HOW TO WRITE C CODE FROM MIPS SOFTWARE#

When you have to use OS-specific calls, use conditional compilation (#ifdef WIN32, etc).

Use standard functions for accessing files. For example, SDL provides types like Uint8, Qt 4 has quint32, etc. OR use types provided by cross-platform library. It is very likely that you'll need some kind of type that is guaranteed to be 4 bytes long (or something like that) - use typedef combined with conditional compilation ('#ifdef WIN32').

Do not rely on compiler-specific data types, like _int32.

For example, last time I checked '%S' behaves differently on msvc and gcc in vswprintf routine. For example, sprintf may have different additional formats that are implemented differently on different platforms. (I know that it is supposed to be a bad practice, but in some scenarios this is useful) They have slightly different implementations, extensions, and different number of parameters.

Be very careful if you decide to use C-style routines (like sprintf) in C++ code.

Which, of course, won't be available on other platforms. For example, MS compiler provides multiple 'safe' (like strcpy_s) versions of standard C-style routines. This more applicable to C library functions, though.

Do not use extensions to standard library (provided by compiler developer).

Do not use compiler-specific pragmas, macros and extensions.

And you should not assume that pointer is 4 bytes large (passing user data pointer into api call scenario) - it will be 8 bytes on 64 bit. Use sizeof (if you need it), or try to avoid having to use size of any type in your code. For example, on msvc sizeof(wchar_t) is 2 bytes.

Do not rely on sizes of standard types.

For example, certain versions of ms compiler have a limit on sizes of string constants, which gcc doesn't have. Even if your code is perfect, compiler might have some kind of unexpected quirk.

'microsoft compiler'), and a linux installation with g++ (or use virtual machine).

#HOW TO WRITE C CODE FROM MIPS SOFTWARE#

If you're doing cross-platform software for windows windows/linux, keep around mingw, visual studio express (i.e.

Keep several compilers nearby, test code regularly on target platforms.

#HOW TO WRITE C CODE FROM MIPS PORTABLE#

What are the things that I should keep in mind to write portable code?

How to write c code from mips