Hi, everybody! I still understand how can I let other people to know what's in my libs? For example, I have organized a lib using D, and want other people to use it. What should I offer except for the LIB. Should I offer the sources which maybe include some modules. I know it is very easy in C/C++. I just offer some header files in C/C++, but what can I do in D.

Somebody can give me some hints. Thanks for your any helps.

zhang wrote:
> Hi, everybody! I still understand how can I let other people to know
> what's in my libs? For example, I have organized a lib using D, and want
> other people to use it. What should I offer except for the LIB. Should I
> offer the sources which maybe include some modules. I know it is very
> easy in C/C++. I just offer some header files in C/C++, but what can I
> do in D. 
> 
> Somebody can give me some hints. Thanks for your any helps.
> 

If your library is opensource, then you might just give the .d files and nevermind the .lib.  D compiles fast, so it's doubtful anyone will mind the extra compilation.

Otherwise if you have some reason to keep the source under wraps and just offer the .lib, then dmd can make d interface files (.di files). The .di files contain all the info someone needs to link to your .lib, and little or no more.
http://www.digitalmars.com/d/dcompiler.html
At the bottom of the page, read "D Interface Files".

Thank you very much! Sorry for my carelessness. I'll read dcompiler.html .

You may also consider giving dsource (http://dsource.org) a try, if you mean to make your library open source. Even if not, maybe Brad hosts your binaries + documentation there, too.

No matter what, you should also set up a webpage for it:
http://www.digitalmars.com/d/howto-promote.html

Kind regards,
Alex

zhang wrote:
> Hi, everybody! I still understand how can I let other people to know
> what's in my libs? For example, I have organized a lib using D, and want
> other people to use it. What should I offer except for the LIB. Should I
> offer the sources which maybe include some modules. I know it is very
> easy in C/C++. I just offer some header files in C/C++, but what can I
> do in D. 
> 
> Somebody can give me some hints. Thanks for your any helps.
> 

Brad, if you're watching this post:

I'm sure you don't, but if you start hosting closed software on dsource ... *shakes fist in rage*

 - Gregor Richards

Alexander Panek wrote:
> You may also consider giving dsource (http://dsource.org) a try, if you mean to make your library open source. Even if not, maybe Brad hosts your binaries + documentation there, too.
> 
> No matter what, you should also set up a webpage for it:
> http://www.digitalmars.com/d/howto-promote.html
> 
> Kind regards,
> Alex
> 
> zhang wrote:
>> Hi, everybody! I still understand how can I let other people to know
>> what's in my libs? For example, I have organized a lib using D, and want
>> other people to use it. What should I offer except for the LIB. Should I
>> offer the sources which maybe include some modules. I know it is very
>> easy in C/C++. I just offer some header files in C/C++, but what can I
>> do in D.
>> Somebody can give me some hints. Thanks for your any helps.
>>

Gregor Richards wrote:
> Brad, if you're watching this post:
> 
> I'm sure you don't, but if you start hosting closed software on dsource ... *shakes fist in rage*
> 
>  - Gregor Richards
> 
> Alexander Panek wrote:
>> You may also consider giving dsource (http://dsource.org) a try, if you mean to make your library open source. Even if not, maybe Brad hosts your binaries + documentation there, too.
>>
>> No matter what, you should also set up a webpage for it:
>> http://www.digitalmars.com/d/howto-promote.html
>>
>> Kind regards,
>> Alex
>>
>> zhang wrote:
>>> Hi, everybody! I still understand how can I let other people to know
>>> what's in my libs? For example, I have organized a lib using D, and want
>>> other people to use it. What should I offer except for the LIB. Should I
>>> offer the sources which maybe include some modules. I know it is very
>>> easy in C/C++. I just offer some header files in C/C++, but what can I
>>> do in D.
>>> Somebody can give me some hints. Thanks for your any helps.
>>>

I think I'm gonna open a new site called dwhore.com, you pay me, I host your closed source app and sell it to the masses. Any takers? :D

Kyle Furlong wrote:
> Gregor Richards wrote:
>> Alexander Panek wrote:
>>> zhang wrote:
>>>> Hi, everybody! I still understand how can I let other people to know
>>>> what's in my libs? For example, I have organized a lib using D, and want
>>>> other people to use it. What should I offer except for the LIB. Should I
>>>> offer the sources which maybe include some modules. I know it is very
>>>> easy in C/C++. I just offer some header files in C/C++, but what can I
>>>> do in D.
>>>> Somebody can give me some hints. Thanks for your any helps.
>>>>
>>> You may also consider giving dsource (http://dsource.org) a try, if you mean to make your library open source. Even if not, maybe Brad hosts your binaries + documentation there, too.
>>>
>>> No matter what, you should also set up a webpage for it:
>>> http://www.digitalmars.com/d/howto-promote.html
>>>
>>> Kind regards,
>>> Alex
>>>
>> Brad, if you're watching this post:
>>
>> I'm sure you don't, but if you start hosting closed software on dsource ... *shakes fist in rage*
>>
>>  - Gregor Richards
>>
> 
> I think I'm gonna open a new site called dwhore.com, you pay me, I host your closed source app and sell it to the masses. Any takers? :D

Wouldn't you be the dpimp in that model?

 - Gregor Richards

Gregor Richards wrote:
> Brad, if you're watching this post:
> 
> I'm sure you don't, but if you start hosting closed software on dsource ... *shakes fist in rage*
> 
>  - Gregor Richards
> 

What really pisses me off is people trying to impose their politics on others, especially when they're free to do the work (and possibly underwrite the expense) of hosting their own site with their own rules.

Brad, go ahead and do what you like, and thanks for all of your work on dsource already.

Dave wrote:
> Gregor Richards wrote:
>> Brad, if you're watching this post:
>>
>> I'm sure you don't, but if you start hosting closed software on dsource ... *shakes fist in rage*
>>
>>  - Gregor Richards
>>
> 
> What really pisses me off is people trying to impose their politics on others, especially when they're free to do the work (and possibly underwrite the expense) of hosting their own site with their own rules.
> 
> Brad, go ahead and do what you like, and thanks for all of your work on dsource already.

I think the DSource policy is open source only.  It says right there on the front page in the banner at the top -- DSource is down right now, but it says something like:  "DSource: Open Source For the D Community".

So I think that makes Brad's intentions with the site pretty clear.  Of course he's free to change his mind.

--bb

Dave wrote:
> Gregor Richards wrote:
>> Brad, if you're watching this post:
>>
>> I'm sure you don't, but if you start hosting closed software on dsource ... *shakes fist in rage*
>>
>>  - Gregor Richards
>>
> 
> What really pisses me off is people trying to impose their politics on others, especially when they're free to do the work (and possibly underwrite the expense) of hosting their own site with their own rules.
> 
> Brad, go ahead and do what you like, and thanks for all of your work on dsource already.

What really pisses me off is when people have no sense of humor whatsoever, and as such take something perfectly innocent and turn it into a political attack.

Oh wait, no, that's right!  It doesn't piss me off, because I actually /do/ have a sense of humor.

 - Gregor Richards