On C/C++ undefined behaviours

[SK]

On Fri, Aug 20, 2010 at 8:46 PM, Walter Bright
<newshound2 at digitalmars.com> wrote:
> SK wrote:
>>
>> Then to make this more concrete, what if D had an option to suspend
>> compilation after the front-end finished?  The resulting executable
>> contains the abstract RTL blobs and the compiler backend, which
>> finishes the job for the specific platform on which the executable is
>> launched.  The final binary is cached for subsequent launches.  You
>> get good machine independence and the approach provides performance
>> wins for operations like vectorizing where you don't know in advance
>> what kind of SSE support you'll find.
>>
>> Hypothetically, why not?
>
> It's an old idea, but I think it's pointless. Instead of caching the
> intermediate code, just cache the source code.
>
>

Huh?

Do you mean to say:
Instead of shipping the intermediate code, always ship source code.
-or-
Instead of caching the binary, just cache the source code.

Neither of those guesses make general sense so I'm afraid I miss your point.