Piotrek wrote:
Don pisze:
Don wrote:
With the druntime project, we now have a run time which is shared
between Tango and Phobos. This is a huge step forward, but it's still
not much use without some common user code.
The highest priorities which I see are, in order:
(1) the C standard
Don wrote:
Please read it again. I'm not asking the question where do we put it?
Rather, to agree that it WILL eventually go SOMEWHERE. If we agree on
that, there are immediate implications. Those modules have some
functions which differ in naming (mostly in case). That's a difference
we can
Don wrote:
Are people OK with some of their code breaking for the sake of unity?
For the math stuff, that would mean name changes on minor functions such
as:
isnormal() - isNormal()
I need a mandate.
My personal point of view (from what I've learned so far) is as follows:
Fortunately
Robert Fraser wrote:
Don wrote:
Please read it again. I'm not asking the question where do we put it?
Rather, to agree that it WILL eventually go SOMEWHERE. If we agree on
that, there are immediate implications. Those modules have some
functions which differ in naming (mostly in case). That's
Don wrote:
Piotrek wrote:
Don pisze:
Don wrote:
With the druntime project, we now have a run time which is shared
between Tango and Phobos. This is a huge step forward, but it's
still not much use without some common user code.
The highest priorities which I see are, in order:
(1) the C
== Quote from Don (nos...@nospam.com)'s article
No, it's a question to the community. I'm the primary maintainer of the
math modules in both libraries. The efforts are straightforwards and not
very time consuming. But I don't think I can break code just because I
have a personal desire for
Don wrote:
Are people OK with some of their code breaking for the sake of unity?
I am absolutely fine with this. Please do make the D platform better!
Don wrote:
Don wrote:
With the druntime project, we now have a run time which is shared
between Tango and Phobos. This is a huge step forward, but it's still
not much use without some common user code.
The highest priorities which I see are, in order:
(1) the C standard library
tango.stdc =
Andrei Alexandrescu wrote:
By the way, what happened to
std.traits and std.typecons? They are two of my faves and are growing as
we speak.
Andrei
std.traits and tango.core.Traits have a number of superficial
differences, such as ReturnType versus ReturnTypeOf, ParameterTypeTuple
versus
Andrei Alexandrescu wrote:
Don wrote:
Piotrek wrote:
Don pisze:
Don wrote:
With the druntime project, we now have a run time which is shared
between Tango and Phobos. This is a huge step forward, but it's
still not much use without some common user code.
The highest priorities which I see
Don wrote:
Are people OK with some of their code breaking for the sake of unity?
For the math stuff, that would mean name changes on minor functions such
as:
isnormal() - isNormal()
I need a mandate.
Aye, I say!
--
Simen
Christopher Wright wrote:
I support it, but I don't use these functions. A few changes in case
wouldn't bother me in any case (except all upper, or small caps).
ᴡʜy ᴀʀe ʏᴏᴜ ᴏᴘᴘosᴇᴅ ᴛo sᴍᴀʟʟ-ᴄᴀᴘs ɪɴ ᴄᴏᴅᴇ?
—Joel Salomon
Don wrote:
With the druntime project, we now have a run time which is shared
between Tango and Phobos. This is a huge step forward, but it's still
not much use without some common user code.
The highest priorities which I see are, in order:
(1) the C standard library
tango.stdc = std.stdc
(2)
Don pisze:
Don wrote:
With the druntime project, we now have a run time which is shared
between Tango and Phobos. This is a huge step forward, but it's still
not much use without some common user code.
The highest priorities which I see are, in order:
(1) the C standard library
tango.stdc =
14 matches
Mail list logo
