Philosophy of how OS API imports are laid out in druntime
Iain Buclaw
ibuclaw at gdcproject.org
Fri Mar 7 09:30:30 PST 2014
On 7 March 2014 09:34, Walter Bright <newshound2 at digitalmars.com> wrote:
> On 3/7/2014 1:03 AM, Iain Buclaw wrote:
>>
>> On 7 March 2014 08:34, Walter Bright <newshound2 at digitalmars.com> wrote:
>>>
>>> On 3/7/2014 12:00 AM, Iain Buclaw wrote:
>>>>
>>>>
>>>> I assume the C headers will remain strictly under core.stdc? So it
>>>> might make sense to transition core.sys -> core.stdc.sys?
>>>
>>>
>>>
>>> I think core.stdc for the Standard C headers can remain the same.
>>>
>>
>> OK - now that has been sorted. What's your opinion on where ports of
>> standard C and system C headers should go?
>>
>
> Standard C => core.stdc
>
> Operating system API = > core? core.sys? core.os? I don't have strong
> feelings about that.
Arch ports, not platform ports.
More information about the Digitalmars-d
mailing list