Thread overview | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
October 18, 2011 D2 port of Tango | ||||
---|---|---|---|---|
| ||||
I just wanted to get the word out about a little project me and a few other people been working on for the few past months, in case anyone feels like helping out (or just as an FYI). This project is the D2 port of the Tango framework library. You can read about it here: https://github.com/SiegeLord/Tango-D2 We are currently a little more than half way done in terms of modules fiddled with. Currently there are 181 modules ported out of approximately 343 (give or take 20). Currently only the dmd compiler and Linux platform are supported... but obviously we want to get all the other platforms/compilers as time goes on. I'm guessing at the current rate of porting we'll be done in about half a year. Now, the project is actually two projects in one. The first project is a D2 port proper that tries to keep API semantics the same as the D1 original. I preside over this aspect, and you can see the rough porting guidelines in the repository. This is the 'd2port' branch in my repository. The second project is a more ambitious effort to rewrite some aspects of Tango without preserving semantics or anything. mtachrono presides over this aspect, so you can talk to him about the motivations behind it. This is the 'master' branch in my repository. That's all. Cheers. -SiegeLord |
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to SiegeLord Attachments:
| On Mon, Oct 17, 2011 at 11:52 PM, SiegeLord <none@none.com> wrote:
> I just wanted to get the word out about a little project me and a few other people been working on for the few past months, in case anyone feels like helping out (or just as an FYI). This project is the D2 port of the Tango framework library. You can read about it here:
>
> https://github.com/haskelSiegeLord/Tango-D2<https://github.com/SiegeLord/Tango-D2>
>
> We are currently a little more than half way done in terms of modules fiddled with. Currently there are 181 modules ported out of approximately 343 (give or take 20). Currently only the dmd compiler and Linux platform are supported... but obviously we want to get all the other platforms/compilers as time goes on. I'm guessing at the current rate of porting we'll be done in about half a year.
>
> Now, the project is actually two projects in one.
>
> The first project is a D2 port proper that tries to keep API semantics the same as the D1 original. I preside over this aspect, and you can see the rough porting guidelines in the repository. This is the 'd2port' branch in my repository.
>
> The second project is a more ambitious effort to rewrite some aspects of Tango without preserving semantics or anything. mtachrono presides over this aspect, so you can talk to him about the motivations behind it. This is the 'master' branch in my repository.
>
> That's all. Cheers.
>
> -SiegeLord
>
Why? What's the point? Why not work on Phobos instead?
|
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to SiegeLord | On 2011-10-18 06:52, SiegeLord wrote: > I just wanted to get the word out about a little project me and a few other people been working on for the few past months, in case anyone feels like helping out (or just as an FYI). This project is the D2 port of the Tango framework library. You can read about it here: > > https://github.com/SiegeLord/Tango-D2 > > We are currently a little more than half way done in terms of modules fiddled with. Currently there are 181 modules ported out of approximately 343 (give or take 20). Currently only the dmd compiler and Linux platform are supported... but obviously we want to get all the other platforms/compilers as time goes on. I'm guessing at the current rate of porting we'll be done in about half a year. > > Now, the project is actually two projects in one. > > The first project is a D2 port proper that tries to keep API semantics the same as the D1 original. I preside over this aspect, and you can see the rough porting guidelines in the repository. This is the 'd2port' branch in my repository. > > The second project is a more ambitious effort to rewrite some aspects of Tango without preserving semantics or anything. mtachrono presides over this aspect, so you can talk to him about the motivations behind it. This is the 'master' branch in my repository. > > That's all. Cheers. > > -SiegeLord This is great, keep up to good work. -- /Jacob Carlborg |
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to SiegeLord | On 2011-10-18 06:52, SiegeLord wrote: > I just wanted to get the word out about a little project me and a few other people been working on for the few past months, in case anyone feels like helping out (or just as an FYI). This project is the D2 port of the Tango framework library. You can read about it here: > > https://github.com/SiegeLord/Tango-D2 > > We are currently a little more than half way done in terms of modules fiddled with. Currently there are 181 modules ported out of approximately 343 (give or take 20). Currently only the dmd compiler and Linux platform are supported... but obviously we want to get all the other platforms/compilers as time goes on. I'm guessing at the current rate of porting we'll be done in about half a year. > > Now, the project is actually two projects in one. > > The first project is a D2 port proper that tries to keep API semantics the same as the D1 original. I preside over this aspect, and you can see the rough porting guidelines in the repository. This is the 'd2port' branch in my repository. Does this use druntime? > The second project is a more ambitious effort to rewrite some aspects of Tango without preserving semantics or anything. mtachrono presides over this aspect, so you can talk to him about the motivations behind it. This is the 'master' branch in my repository. Do you have any examples of this, what's changed? > That's all. Cheers. > > -SiegeLord -- /Jacob Carlborg |
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to SiegeLord | Good job.
> The first project is a D2 port proper that tries to keep API semantics This is the 'd2port' branch in my repository.
>
> The second project is a more ambitious effort to rewrite some aspectsThis is the 'master' branch in my repository.
Why isn't it the other way around?
|
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to Caligo | > Why? What's the point? Why not work on Phobos instead?
Well D1 projects could be ported to D2 much more easily, e.g. Yage.
|
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to SiegeLord | Greate news. I wait for it for a long time. |
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to Caligo | Caligo Wrote:
> Why? What's the point? Why not work on Phobos instead?
Aside from the obvious philosophical differences, which I am NOT going to get into, porting D1 projects is an important reason.
-SiegeLord
|
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to Trass3r | Trass3r Wrote:
> Why isn't it the other way around?
Just a historical oddity.
-SiegeLord
|
October 18, 2011 Re: D2 port of Tango | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jacob Carlborg | Jacob Carlborg Wrote: > Does this use druntime? Yes, although a Tango specific runtime (compatible with druntime) will probably be an option some day too. Still, right now you can safely use (modulo my imperfect testing) Phobos and Tango modules together in a single program. > Do you have any examples of this, what's changed? The biggest difference right now is the near-complete rewriting of the tango.net package. You'd have to get a hold of mtachrono to see what roadmap he has. -SiegeLord |
Copyright © 1999-2021 by the D Language Foundation