Errors - Re: Signals and Slots

[Kyle Furlong]

Walter Bright wrote:
> Chris Miller wrote:
>> I think this is finally a real mixin limitation being exposed. You 
>> probably only tested std.signals inside the signals.d source file, 
>> where the mixin had access to std.signals' imports.
> 
> I plead guilty. My test suite is now corrected.
> 
>> But use std.signals from another file and the mixin cannot access 
>> std.signal's imports because it's accessing the mixed-in scope. In 
>> other words, I think to remove these errors, std.signals' imports 
>> would need to be imported inside the mixin template (hack?), or change 
>> how mixins work.
> 
> The fix is straightforward, in std\signals.d just make the imports public:
> 
>> public import std.stdio;
>> public import std.c.stdlib;
>> public import std.outofmemory;

Walter, please don't pull a GW here.