boB wrote:
>>> Oh - to be a bit crass ``compiling'' is the process of
>
>To be a bit factual, "compiling" is the process of creating bloatware,
>regardless of compiler and OS used. To avoid bloat, always assemble. ;)

Whenever one choose to "compile" the actuall process involves several
things, ex. linking, creating object code (.obj files) and as a last part
creating a runable program from the object code (or in some cases where no
object code is created from the actuall code you wrote or into ASMbler
which then transfers inro executable code).
Whenever you choose to "asemble" a program in ex. Turbo ASM or Microsoft
ASM you will also create .obj files and then runable code from the object
code.
If one would use ex. "debug" or program a cellular phone then there would
not be any object code. There might also be the option to never create the
object code in some ASMblers. The object code is mostly used if you want to
include it in a program environment that doesn't allow inline ASM. Examples
are Linux GCC/DJGPP - I'll quote an unknown source "I've discovered some
people that actually don't have an assembler [he/she refers to an inline
one], poor bastards". Or if you believe that you have a ASMbler that can
create better code then your highlevel compiler. (True if you for instance
want to create a program using MMX instructions, or some other new made
invention with your old normal compiler).
Lets see was it this year that I'm supposed to learn how to program a
compiler at university? <Searching for papers> Ah, I see it's a bit into
the future (in Mars-May). First I'll need to learn how to make an OS (I can
see several interesting discussion with the teachers arising what an OS
actually is - one thought that as soon as you load a TSR it would be a
completly new OS when I discussed it with him earlier on).

Is this OT? But nothing at all was On Topic (no mails at all!) for an
entire day yesterday :(
I'll guess it doesn't bother you too much (only a few people are reading
now anyway, right) ;)
//Bernie

To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with 
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.

Reply via email to