Is d support for extern (D) void core.rt.FunctionA(ParameterList);
I want to know...

And I don't find the document for keyword "alias" in the Language Specification. If someone know, please tell me.

Please post these types of question in the 'learn' newsgroup.

Yonggang Luo wrote:
> Is d support for extern (D) void core.rt.FunctionA(ParameterList);
> I want to know...

Not sure what you mean. Perhaps you want to do this:

import core.rt : FunctionA;

> And I don't find the document for keyword "alias" in the Language Specification.
> If someone know, please tell me.

It's on the 'declarations' page.

Don Wrote:

> Please post these types of question in the 'learn' newsgroup.
> 
> Yonggang Luo wrote:
> > Is d support for extern (D) void core.rt.FunctionA(ParameterList);
> > I want to know...
> 
> Not sure what you mean. Perhaps you want to do this:
> 
> import core.rt : FunctionA;
> 
> > And I don't find the document for keyword "alias" in the Language Specification. If someone know, please tell me.
> 
> It's on the 'declarations' page.
> 

Oh , no, I means there is not such a file that name core.rt.d;

Because I want to separate some files from the "Library" that I want to distributed.

Yonggang Luo Wrote:

> Oh , no, I means there is not such a file that name core.rt.d;
> 
> Because I want to separate some files from the "Library" that I want to distributed.

Modules rely on filesystem, so you should have core/rt.d somewhere or you won't be able to compile this. Include option determines where to search packages/modules.

Yonggang Luo wrote:
> Don Wrote:
> 
>> Please post these types of question in the 'learn' newsgroup.
>>
>> Yonggang Luo wrote:
>>> Is d support for extern (D) void core.rt.FunctionA(ParameterList);
>>> I want to know...
>> Not sure what you mean. Perhaps you want to do this:
>>
>> import core.rt : FunctionA;
>>
>>> And I don't find the document for keyword "alias" in the Language Specification.
>>> If someone know, please tell me.
>> It's on the 'declarations' page.
>>
> 
> Oh , no, I means there is not such a file that name core.rt.d;
> 
> Because I want to separate some files from the "Library" that I want to distributed.

Then call it core.rt.di instead of core.rt.d.

I means to support for this, because of this, then we can hidden something that we don't want to see.

When you just want to see that API, and not the detail implement.
And also it can reduce the redundant thinking about what does this module meaning and that module meaning. Because we just see the API.

This is useful if you don't like to show all the things to the user.

Yonggang Luo Wrote:

> I means to support for this, because of this, then we can hidden something that we don't want to see.
> 
> When you just want to see that API, and not the detail implement.
> And also it can reduce the redundant thinking about what does this module meaning and that module meaning. Because we just see the API.
> 
> This is useful if you don't like to show all the things to the user.

dmd supports automatic generation of .di files which are similar to C .h files. Or you can write .di files manually. Or you can write separate core/rt.d with just declarations and another core/rt.d with implementation.