On 2015-01-08 22:25, Andrei Alexandrescu wrote:

> Yah, as I said it's a project.

Can we at least generate the documentation on multiple platforms, just to make sure we got all modules.

-- 
/Jacob Carlborg

On 1/8/2015 7:41 AM, Andrei Alexandrescu wrote:
> If we get real cocky we might insert for each symbol a LUCKY link googling for the
> header name and symbol name.


Livin' on the edge!

On 1/8/2015 1:01 PM, Steven Schveighoffer wrote:
> core.stdc.config is not technically a standard C header, and it seems pretty
> strange. I'm going to leave that one alone unless someone objects.

Yeah, the mere existence of that module grates.

On 1/9/15 2:14 AM, Jacob Carlborg wrote:
> On 2015-01-08 22:01, Steven Schveighoffer wrote:
>
>> core.stdc.config is not technically a standard C header, and it seems
>> pretty strange. I'm going to leave that one alone unless someone objects.
>
> Shouldn't this then be documented like any other druntime/Phobos module.

Sure, that is fine by me. But I'm not going to do it, as I don't know what it's for :)

-Steve

On 1/8/15 4:01 PM, Steven Schveighoffer wrote:
> On 1/8/15 10:41 AM, Andrei Alexandrescu wrote:
>> On 1/8/15 4:18 AM, Steven Schveighoffer wrote:
>
>>> Thoughts? I can put together a pull for core.stdc.* if it makes sense.
>>
>> Blurb LGTM, please make it happen. Also let's experiment with the ///'s.
>
> Just to put a semaphore on this, I'm partway through doing this, please
> don't someone else do it too, it's tedious work :)

https://github.com/D-Programming-Language/druntime/pull/1091

-Steve

On Thursday, 8 January 2015 at 12:18:37 UTC, Steven Schveighoffer wrote:
> One thing that may be misleading about this -- our headers don't include *everything* from C-land.

What's missing? They should just match their C counterparts.

On 1/9/15 12:08 PM, Martin Nowak wrote:
> On Thursday, 8 January 2015 at 12:18:37 UTC, Steven Schveighoffer wrote:
>> One thing that may be misleading about this -- our headers don't
>> include *everything* from C-land.
>
> What's missing? They should just match their C counterparts.

Perhaps they do, I don't think we should guarantee it though. For instance, a macro may not be suited to be included in D because we have better options.

-Steve

On 1/9/15 10:10 AM, Steven Schveighoffer wrote:
> On 1/9/15 12:08 PM, Martin Nowak wrote:
>> On Thursday, 8 January 2015 at 12:18:37 UTC, Steven Schveighoffer wrote:
>>> One thing that may be misleading about this -- our headers don't
>>> include *everything* from C-land.
>>
>> What's missing? They should just match their C counterparts.
>
> Perhaps they do, I don't think we should guarantee it though. For
> instance, a macro may not be suited to be included in D because we have
> better options.

Maybe Calypso could be used for that? -- Andrei

On 1/9/15 12:08 PM, Martin Nowak wrote:
> On Thursday, 8 January 2015 at 12:18:37 UTC, Steven Schveighoffer wrote:
>> One thing that may be misleading about this -- our headers don't
>> include *everything* from C-land.
>
> What's missing? They should just match their C counterparts.

Andrei had the idea to put the blurb in one place as a macro, so we can change it quite easily if you can think of a better statement.

See here: https://github.com/D-Programming-Language/dlang.org/pull/752

-Steve

On 1/9/15 10:46 AM, Steven Schveighoffer wrote:
> On 1/9/15 12:08 PM, Martin Nowak wrote:
>> On Thursday, 8 January 2015 at 12:18:37 UTC, Steven Schveighoffer wrote:
>>> One thing that may be misleading about this -- our headers don't
>>> include *everything* from C-land.
>>
>> What's missing? They should just match their C counterparts.
>
> Andrei had the idea to put the blurb in one place as a macro, so we can
> change it quite easily if you can think of a better statement.
>
> See here: https://github.com/D-Programming-Language/dlang.org/pull/752

Stuff's up! http://dlang.org/library-prerelease/core/stdc/complex.html. I couldn't get rid of the darn space between the header name and the period. -- Andrei