This version is compatible with DMD .148 and, as of 0.14, should also compile on Linux with DMD.  There have also been some additions to std.atomic, and the std.math package is coming along fairly well.  It can be obtained in the usual place:

http://www.dsource.org/projects/ares/

Please see the Ares forum or the included changelog for a more detailed list of updates.


Sean

One thing that I do not understand is why 'the second coming' of phobos is needed?

Sean Kelly wrote:
> This version is compatible with DMD .148 and, as of 0.14, should also compile on Linux with DMD.  There have also been some additions to std.atomic, and the std.math package is coming along fairly well.  It can be obtained in the usual place:
> 
> http://www.dsource.org/projects/ares/
> 
> Please see the Ares forum or the included changelog for a more detailed list of updates.
> 
> 
> Sean

bobef wrote:
> One thing that I do not understand is why 'the second coming' of phobos is needed?
> 
> Sean Kelly wrote:
> 
>> This version is compatible with DMD .148 and, as of 0.14, should also compile on Linux with DMD.  There have also been some additions to std.atomic, and the std.math package is coming along fairly well.  It can be obtained in the usual place:
>>
>> http://www.dsource.org/projects/ares/
>>
>> Please see the Ares forum or the included changelog for a more detailed list of updates.
>>
>>
>> Sean

I appreciate the efforts being done, but I just can't go thru the trouble of literally *replacing* phobos on my system with Ares. I just can't be bothered with that.
I don't recompile phobos or do any of that crazy stuff (not to mention compile a linux kernel!!)

I recently discovered that Mango is actually not only for server side programming but a very good library/framework.

What I'm trying to say is, why not instead of replacing phobos *from scratch*, just build a usable framework on top of it!!

Sean,
what license does Ares use?
As of Ares 0.13 I couldn't find any file with clear license.
And the most strange thing is that some files from io does have
BSD-license with advertising clause which appears to apply to
only 2 or 3 files
Regards,
Todor



On Mon, 27 Feb 2006 02:44:55 +0200, Sean Kelly <sean@f4.ca> wrote:

> This version is compatible with DMD .148 and, as of 0.14, should also compile on Linux with DMD.  There have also been some additions to std.atomic, and the std.math package is coming along fairly well.  It can be obtained in the usual place:
>
> http://www.dsource.org/projects/ares/
>
> Please see the Ares forum or the included changelog for a more detailed list of updates.
>
>
> Sean

Hasan Aljudy wrote:

> I appreciate the efforts being done, but I just can't go thru the trouble of literally *replacing* phobos on my system with Ares. I just can't be bothered with that.
> I don't recompile phobos or do any of that crazy stuff (not to mention compile a linux kernel!!)

I am sure one would not try to replace phobos without a really good reason... I just wish I knew this reason...

Hasan Aljudy wrote:
> 
> I appreciate the efforts being done, but I just can't go thru the trouble of literally *replacing* phobos on my system with Ares. I just can't be bothered with that.
> I don't recompile phobos or do any of that crazy stuff (not to mention compile a linux kernel!!)
> 
> I recently discovered that Mango is actually not only for server side programming but a very good library/framework.
> 
> What I'm trying to say is, why not instead of replacing phobos *from scratch*, just build a usable framework on top of it!!

Largely because some of my issues with Phobos are fairly low-level, and I wanted to attempt building a "better" standard library from the ground up.  I've considered having Phobos run on top of Ares in a compatibility area, but as I don't actually use Phobos for anything it would be a lot of work for very little return.  Beginning with the next release I'll probably ship a pre-built Linux library just as I'm doing for Windows. It's really just a matter of automating the Linux build process a bit better--I have the whole process down to a single batch file on Windows.


Sean

Todor Totev wrote:
> Sean,
> what license does Ares use?

Sorry about that.  I'll get file headers in before the next release. The C headers are public domain, and what's in 'std' is subject to some form of the artistic license.  That is, you can do whatever you want with the code, but please leave module headers in place (ie. don't claim the source code is yours).

> As of Ares 0.13 I couldn't find any file with clear license.
> And the most strange thing is that some files from io does have
> BSD-license with advertising clause which appears to apply to
> only 2 or 3 files

The io modules are from Mango and are subject to whatever restrictions Kris has placed on them.  I'll see about providing consistent license language for the next release.  What will probably happen is modules will have an author to attribute the work to but the license will be otherwise identical.  Modules imported from Phobos are another consideration, but I think this approach should apply there as well.


Sean

Sean Kelly wrote:
> Todor Totev wrote:
>> Sean,
>> what license does Ares use?
> 
> Sorry about that.  I'll get file headers in before the next release.

I've added licenses to modules that lacked them.  std.math.special still needs one, but it's from Don's MathExtra library so I'll need to sort that out separately.


Sean

Sean Kelly wrote:
> Sean Kelly wrote:
>> Todor Totev wrote:
>>> Sean,
>>> what license does Ares use?
>>
>> Sorry about that.  I'll get file headers in before the next release.
> 
> I've added licenses to modules that lacked them.  std.math.special still needs one, but it's from Don's MathExtra library so I'll need to sort that out separately.

Actually I don't care. Public domain or something like the Phobos license is fine by me. But as short as possible -- I really *hate* those files where there's 100 lines of legalese and 2 lines of code.

What I'd really like to find is some kind of "non-infect" free license for libraries. That is, you can do anything you like with this code, except that if you redistribute the source code AS SOURCE CODE, it must remain with the same license. So that if it's included in a GPL project, that single file doesn't get GPLed, and if it's in a commercial library where the source is sold, that single file remains free.
But since I don't know of any license that does that, any unrestricted license (including public domain) will do.

Don Clugston wrote:
> Sean Kelly wrote:
>> Sean Kelly wrote:
>>> Todor Totev wrote:
>>>> Sean,
>>>> what license does Ares use?
>>>
>>> Sorry about that.  I'll get file headers in before the next release.
>>
>> I've added licenses to modules that lacked them.  std.math.special still needs one, but it's from Don's MathExtra library so I'll need to sort that out separately.
> 
> Actually I don't care. Public domain or something like the Phobos license is fine by me. But as short as possible -- I really *hate* those files where there's 100 lines of legalese and 2 lines of code.
> 
> What I'd really like to find is some kind of "non-infect" free license for libraries. That is, you can do anything you like with this code, except that if you redistribute the source code AS SOURCE CODE, it must remain with the same license. So that if it's included in a GPL project, that single file doesn't get GPLed, and if it's in a commercial library where the source is sold, that single file remains free.

The BSD (artistic) license is about as close as I've found, and is what I'm using for the Ares source for pretty much the same reason as you've indicated--I really don't care what people do with my code so long as they don't claim to have written it.

> But since I don't know of any license that does that, any unrestricted license (including public domain) will do.

Thanks.


Sean