Andrey Vlassov wrote: > If you ask them what really happens when they click "Compile" or "Run" > you will get wrong answer.
Half of what you wrote about compilation sequence is obviously wrong. If you ever going to teach people about the topic, please first make clear how it really works for yourself. > For most IDE the sequence is next: > > 1. save file > 2. regenerate makefile (if it required) > 3. run "make" (or other equivalent) > 4. "make" runs compiler > 5. compiler takes for example C++ code (.cpp) > 6. compiler runs preprocessor (.cpp) > 7. compiler converts C++ into C (.c) > 8. compiler runs C optimizer (.c) > 9. compiler converts C into ASM (.asm) > 10. compiler runs ASM optimizer (.asm) > 11. compiler runs ASM compiler (.obj) > 12. compiler runs linker (.exe/.com/.bin/.ihx/.out) > > But system can get even more complicated (GNU Compiler Collection) > > C++ -> C > Objective-C -> C > Pascal -> C > Ada -> C > Java -> C > Fortran -> C > C -> Assembly > Assembly -> binary code ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
