On Mon, 21 May 2012 05:12:32 -0700, dawg <[email protected]> wrote:
On Tuesday, 15 May 2012 at 06:46:58 UTC, Adam Wilson wrote:
On Mon, 14 May 2012 23:11:50 -0700, Jonathan M Davis
<[email protected]> wrote:
On Monday, May 14, 2012 23:03:20 Adam Wilson wrote:
I have updated the make files so that only core.thread and
core.sync.* are
run through DI generation. ALL other core.* modules are copied into
the
import directory now.
I assume that object.di and core/thread.di are being used rather than
their
corresponding .d files being run through the .di generation? They
already have
hand-crafted .di files.
- Jonathan M Davis
The funny thing is that core.thread.di was being run through the DI
generator in the old make file. I had left it that way, I have posted a
commit that moves it to the copy section.
I did that so that the same di generation logic is applied to
the handwritten import files. Currently I don't really expect any
difference though.
Currently, there isn't any difference, however, once DI generation is
changed to strip out function implementations it could change
significantly. There is even talk of building a limited amount of semantic
analysis into DI generation. Because of this, relying on the current DI
generation in the future would not be a good idea; these changes are in
preparation for future DI changes.
--
Adam Wilson
IRC: LightBender
Project Coordinator
The Horizon Project
http://www.thehorizonproject.org/