Thread: Cross (compiler | OS) && reuseable code

Hello guys, here I come with a new problem!
*sigh* such a trouble-maker... *_*"


1. Btw, is there any tips to make our code reuseable?

2. How to organize it well?

For example, we have the header file "memoryPool.h", the source "memoryPool.c" and the OOP templated class C++ version "memoryPool.cpp"

3. Where we should put those files? Should we put those file in: project-directory\include or compiler-directory\include?

4. How about if we are working on different compilers?


5. Anybody know what is the indicated #defines that we are now working on:
- GCC / MinGW
- LCC
- TCC
- eC
- Digital Mars C++
- Microsoft Visual C++ 6/2005/2008
- Pelles C
- Bloodshed Dev-C++ == MinGW?
- Borland C++ 5.5/2005/new version?


And the last question, ...

6. How to know if our code is cross platform?

7. Should we test it on different OS(es)?

8. Or is there any #defines?


Btw, thanks in advance. phew...

> 1. Btw, is there any tips to make our code reuseable?
> 2. How to organize it well?
Understand the difference between
a) ANSI
b) POSIX
c) Platform specific.
Don't mix APIs from different domains in the same code. Ideally, 90% of the code should be code you've written and ANSI. Isolate the rest in "compatibility" layers which will minimise the amount of rework in case you need to port from one system to another.

> 3. Where we should put those files? Should we put those file in: project-directory\include or compiler-directory\include?
NEVER in the compiler include directory.
If you're writing a library which others will use, then it would go (in Unix terms) into /usr/local/include and /usr/local/lib

> 4. How about if we are working on different compilers?
Always a good idea
It keeps you honest and stops you slipping in any implementation defined or specific compiler extensions.

> 5. Anybody know what is the indicated #defines that we are now working on:
http://predef.sourceforge.net/

> 6. How to know if our code is cross platform?
By trying it on various systems.

Oops.. I forget!

9. Are std* functions portable?

^_^" Thank you for your response, that's very very help me so much.

Anybody know what is the indicated #defines that we are now working on <-- bad grammars?

*OMG* http://predef.sourceforge.net/precomp.html There are a LOT of compilers out there!!

Originally Posted by audinue

Oops.. I forget!

9. Are std* functions portable?

You mean stuff like stdio.h, stdlib.h, time.h etc: yes, from a calling perspective they are. That's not to say that stdio.h functions can't contain extensions that are non-portable [e.g. printf() supports %b for binary or some such, whilst most other compilers don't - a more common example would be the fflush(stdin) that actually does clear the input buffer, whilst the standard only says that it will flush ouput data].

--
Mats

You mentioned C++, so if you mean all of the stuff in the std:: namespace, yes, that is generally portable too.