View previous topic :: View next topic |
Author |
Message |
keinfarbton
Joined: 03 Dec 2005 Posts: 224 Location: Stuttgart - Germany
|
Posted: Thu Jun 15, 2006 6:48 pm Post subject: porting app to ares |
|
|
I am interested in trying ares, but it is not an easy task.
I often use format and there is nothing such in ares.
Now I wonder, why not all functionality from phobos is in ares. Is there a reason not to copy all the functionality from phobos into ares?
It should be possible to copy phobos completely into a phobosstd package and deprecate these functions and classes, which are reimplemented or moved into the ares packages. So porting should be much more easy. Especially if you know that really all functionality exists. |
|
Back to top |
|
|
sean
Joined: 24 Jun 2004 Posts: 609 Location: Bay Area, CA
|
Posted: Thu Jun 15, 2006 9:23 pm Post subject: |
|
|
I've considered doing this in the past and have avoided it thus far largely for maintenance reasons and because I'm leery of people becoming too comfortable with being able to both at the same time. But perhaps it's the right approach after all. I'll look into it for the next release. |
|
Back to top |
|
|
keinfarbton
Joined: 03 Dec 2005 Posts: 224 Location: Stuttgart - Germany
|
Posted: Fri Jun 16, 2006 8:35 am Post subject: |
|
|
Quote: | I'll look into it for the next release. |
That's great.
I think, only with the minimum of phobos's functionality, ppl will give it a try. If you start and see, there is "missing" this and that, they are going back to phobos. And the definition of what is "missing" is what phobos allready contains |
|
Back to top |
|
|
|