On 24 September 2013 15:32, eles <e...@eles.com> wrote:
> On Tuesday, 24 September 2013 at 14:16:53 UTC, Johannes Pfau wrote:
>>
>> Am Tue, 24 Sep 2013 16:02:11 +0200
>> schrieb "eles" <e...@eles.com>:
>>
>>> Hi,
>>>
>>> After compiling/installing the HEAD version of gdc in /opt/gdc4.9, I
>>> have:
>>> [...]
>>
>>
>> Those files should be in
>> /opt/gdc-4.9/include/d/4.9.0/x86_64-unknown-linux-gnu/
>
>
> Indeed, but only the .di files, nothing about the .d
>
> $ls /opt/gdc-4.9/include/d/4.9.0/x86_64-unknown-linux-gnu/core/
> atomic.di cpuid.di exception.di memory.di simd.di sync time.di
> bitop.di demangle.di math.di runtime.di stdc sys vararg.di
>
> $find . -name 'atomic.d*'
> ./include/d/4.9.0/x86_64-unknown-linux-gnu/32/core/atomic.di
> ./include/d/4.9.0/x86_64-unknown-linux-gnu/core/atomic.di
>
> which is OK, as the .d should not be required, but still it is an asymmetry
> wrt phobos.
IIRC, the idea behind was being that compiler generated interface
files produced would emit only relevant declarations for the target
(ie: version(X86) { ... } else version (X86_64) { ... } would be
condensed down to just one or the other). So far this has not
happened - but then again, not much has been done in the way of
cleaning up what gets spewed out of compiler generated interface files
either...
--
Iain Buclaw
*(p < e ? p++ : p) = (c & 0x0f) + '0';
