The Death of D. (Was Tango vs Phobos)

[Jarrett Billingsley]

"Jarrett Billingsley" <kb3ctd2 at yahoo.com> wrote in message 
news:g82uob$1mg2$1 at digitalmars.com...
> "Walter Bright" <newshound1 at digitalmars.com> wrote in message 
> news:g82ua5$1l6d$1 at digitalmars.com...
>> Sean Kelly wrote:
>>>> What specifically I'd like from the Tango team is explicit permission 
>>>> for the Phobos team to go over the Tango code and be able to copy/use 
>>>> whatever portions of it are necessary to get the two libraries to have 
>>>> a compatible core, and to relicense those parts under the corresponding 
>>>> Phobos license.
>>>
>>> I think this is arguably a reasonable first step, but working towards a 
>>> compatible core still means two separate cores, which means not being 
>>> able to use Tango and Phobos together in the same app.  So I'll admit to 
>>> not completely understanding the reasoning behind this approach, but 
>>> it's the only option so I'm happy to comply.  Frankly, I don't want to 
>>> be stuck maintaining the Tango runtime from now until doomsday anyway 
>>> :-)
>>
>> If the cores are compatible at the API level, then one should be able to 
>> mix and match Tango/Phobos user level modules.
>
> Why one would want to do that is beyond me.

No, don't interpret this as standard-library-fanboyism.  By this I mean that 
even if you _could_ import modules from both phobos and tango, it would be 
next to impossible to use them together.  They each have their own types, 
functions etc. for anything more complex than string manipulations and math 
(and even there they differ).  You can't use a std.stream.Stream and a 
tango.io.Conduit together.  You use one or the other.  Hence, nothing has 
been solved.