Request for Review: DI Generation Improvements

kenji hara k.hara.pg at gmail.com
Tue May 15 02:51:44 PDT 2012


Old days import/core/thread.di was generated from src/core/thread.d .
Current import/core/thread.di is generated from src/core/thread.*di* .

Kenji Hara

2012/5/15 Jonathan M Davis <jmdavisProg at gmx.com>:
> On Monday, May 14, 2012 23:46:08 Adam Wilson wrote:
>> On Mon, 14 May 2012 23:11:50 -0700, Jonathan M Davis <jmdavisProg at gmx.com>
>>
>> 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.
>
> Well, if that works... It's weird though, because there's no reason to have a
> thread.di if it's not used, and as I understand it, some work was being done
> that required some of Thread's internals _not_ be in the .di file, but I don't
> remember the details, and I don't know where that stands.
>
> - Jonathan M Davis


More information about the Digitalmars-d mailing list