DI Generation Needs your Help!

so so at so.so
Mon Dec 19 04:30:27 PST 2011


On Mon, 19 Dec 2011 14:11:31 +0200, so <so at so.so> wrote:

> On Mon, 19 Dec 2011 10:11:25 +0200, Adam Wilson <flyboynw at gmail.com>  
> wrote:
>
>> Everything else is left alone. Templates and mixins are not addressed  
>> with this code and *should* not be modified. That's where I need your  
>> help, the test cases I have written cover some basic scenarios but I  
>> don't have the capability to test these changes with the diverse code  
>> base that the community has created.
>
> I am not exactly sure about your problem with templates and mixins but  
> i'll give it a try regardless :)
> Since with templates there is no distinction between definition and  
> decleration,
> exposing them IMO should be solely based on thier module access  
> signatures.
>
> private struct A() // hide
> public struct B()  // expose
>
> Now if B or some another exposed structure in ".di" should call A,
> compiler will take care of it by outputting an error as usual.

One last thing!
Interfaces shouldn't have any business with "export", they should be  
treated just like templates.


More information about the Digitalmars-d mailing list