[TYPES] Declarative vs imperative
dreamingforward at gmail.com
Tue Apr 23 13:02:59 EDT 2013
>> But there are no details left out. Neither the computer nor compiler
>> "fills in the gaps". What computing devices are you talking about?
>> At every step, at the various levels of abstraction, from the
>> high-level source code, to the the binary executable, there is a
>> complete and detailed "transformation" logic. It will compile down
>> to the same machine code *every* time, if it's working properly.
> Are you claiming, then, that all those fancy optimization flags I can pass to my C compiler don't actually do anything? Or that (say) -fomit-frame-pointer is unfaithful to the "complete and detailed transformation logic"? Better file a bug report.
I well aware of compiler flags and was not implying at all that they
don't do anything. What I was saying is that the compilers output is
deterministic. If you use the same flags and the same source, you
will get the same output -- unless you're suggesting some *magic
happens here* event.
More information about the Types-list