On Fri, 2011-02-18 at 14:27 +0100, Gour wrote:
> On Fri, 18 Feb 2011 12:15:48 +0000
> Russel Winder <russel@russel.org.uk> wrote:
> 
> > I have not used Waf for a D project, just for C++ and LaTeX ones, so I am not sure the state of play there.
> 
> Do you use SCons for D projects?

Yes and no.  My "projects" that have D code are not a collection of source code that gets built into artefacts and possibly installed -- the ideal situation for Waf -- they are collections of programs each of which is compiled and run independently -- a hard problem for Waf, but a sweet spot for SCons.

> > Someone, definitely not me (*), will have to contact Thomas Nagy to ask who to contact to get D tool development.
> 
> Being busy with other things I put my waf-list subscription into web-only mode.
> 
> > I try and avoid using CMake, so have no idea what the state of play there is.
> 
> OK.
> 
> > (*) Thomas has banned me from the Waf Google group so I am not able to monitor or contribute to the Waf eco-system.  Which is irritating as I really quite like Waf.
> 
> Really?
> 
> What happened?

I think Thomas took exception to me doing a compare and contrast of SCons and Waf and then contributing to the SCons project as well as the Waf project.  I surmise that he thinks I am SCons advocate trying to destroy Waf.  However as he won't communicate with me via any channel I have tried, I don't actually know why he has banned me.  But being banned from a Google group completely excludes you from any access.  I had been getting email from the group though, but when I emailed Thomas about something, he cut that off as well.  Basically it seems he wants to exclude me from any form of interaction in the Waf community.  I keep thinking of "why cut off your finger to spite your nose".

> I've noticed, when suggesting some improvements to Waf , via IRC, that
> he tend to be (sometimes) a little bit non-flexible, but
> banning... :-(

I've given up worrying about it.   All the clients I have moved to using Waf just don't bother to contribute back the things they develop for their Waf use as a form of existential protest.

Anyway this is really rather off-topic for this list!


-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@russel.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Documentation isn't updated to include std.datetime and core.time.

Walter Bright Wrote:

> Now with 64 bit Linux support! (Though expect problems with it, it's brand new.)
> 
> 
> http://www.digitalmars.com/d/1.0/changelog.html http://ftp.digitalmars.com/dmd.1.067.zip
> 
> http://www.digitalmars.com/d/2.0/changelog.html http://ftp.digitalmars.com/dmd.2.052.zip

On Friday, February 18, 2011 11:23:17 Jesse Phillips wrote:
> Documentation isn't updated to include std.datetime and core.time.

The documentation in the zip file looks updated, but what's on www.digitalmars.com definitely hasn't been updated.  Other modules, such as std.string, std.array, and std.file which have had definite API changes are the same as 2.051 on the website.

www.d-programming-language.org has up-to-date documentation, but it's currently built off of the git version, not the most recent release, so while it may be correct now, it's going to drift - unless Andrei changes what he's doing with it and makes it the last release. But I think that he's still experimenting with the site, so it's still in flux and not really intended to be the place to go to look up info on D yet, I believe.

- Jonathan M Davis

On 2011-02-18 11:18, Walter Bright wrote:
> Now with 64 bit Linux support! (Though expect problems with it, it's
> brand new.)
>
>
> http://www.digitalmars.com/d/1.0/changelog.html
> http://ftp.digitalmars.com/dmd.1.067.zip
>
> http://www.digitalmars.com/d/2.0/changelog.html
> http://ftp.digitalmars.com/dmd.2.052.zip

It's amazing how each new release fixes more and more bugs. Keep up the good work.

-- 
/Jacob Carlborg

Walter Bright wrote:
> Now with 64 bit Linux support! (Though expect problems with it, it's brand new.)
> 
> 
> http://www.digitalmars.com/d/1.0/changelog.html
> http://ftp.digitalmars.com/dmd.1.067.zip
> 
> http://www.digitalmars.com/d/2.0/changelog.html
> http://ftp.digitalmars.com/dmd.2.052.zip

Eleven man-months to implement a 64-bit backend is pretty impressive, I reckon. Contratulations, Walter!

BTW despite the emphasis on D2, this release has one of the highest number of D1 bugfixes, ever.

== Quote from Don (nospam@nospam.com)'s article
> Walter Bright wrote:
> > Now with 64 bit Linux support! (Though expect problems with it, it's
> > brand new.)
> >
> >
> > http://www.digitalmars.com/d/1.0/changelog.html http://ftp.digitalmars.com/dmd.1.067.zip
> >
> > http://www.digitalmars.com/d/2.0/changelog.html http://ftp.digitalmars.com/dmd.2.052.zip
> Eleven man-months to implement a 64-bit backend is pretty impressive, I
> reckon. Contratulations, Walter!
> BTW despite the emphasis on D2, this release has one of the highest
> number of D1 bugfixes, ever.

Since when was it even 11?  I thought the first 64 commits weren't until June of last year.

Fantastic news! Well done once again to the whole team.

Now that the 64-bit bugbear is in the bag (along with a big pile of bugs), what is next? Is there a list somewhere detailing the planned language/toolchain changes that will make it into D2? Are we converging on a stable release of the language anytime soon?

In particular, are there any plans to re-examine the tail-const issue in light of the compiler patch proposed by Michel Fortin in his post: "const(Object)ref is here!" back in December?

Some other issues I assume are still in flux (and can remember) are:
* Tweaks to usability of const/immutable/shared.
* Tweaks to usability of nothrow, pure, etc.
* Rollout of const, nothrow, pure, etc thoughout phobos.
* Fate of the delete keyword.
* Fate of the scope keyword used in object declaration and function parameters.
* Meaning of in keyword for function parameters. Is it just const, and if so, why not just use const?

I don't have (much) of a personal agenda here - I just want the rough edges smoothed off and a stable language.


-- 

Graham St Jack

Am 21.02.2011 01:51, schrieb Graham St Jack:
> Fantastic news! Well done once again to the whole team.
>
> Now that the 64-bit bugbear is in the bag (along with a big pile of
> bugs), what is next? Is there a list somewhere detailing the planned
> language/toolchain changes that will make it into D2? Are we converging
> on a stable release of the language anytime soon?
>
> In particular, are there any plans to re-examine the tail-const issue in
> light of the compiler patch proposed by Michel Fortin in his post:
> "const(Object)ref is here!" back in December?
>
> Some other issues I assume are still in flux (and can remember) are:
> * Tweaks to usability of const/immutable/shared.
> * Tweaks to usability of nothrow, pure, etc.
> * Rollout of const, nothrow, pure, etc thoughout phobos.
> * Fate of the delete keyword.
> * Fate of the scope keyword used in object declaration and function
> parameters.
> * Meaning of in keyword for function parameters. Is it just const, and
> if so, why not just use const?
>
> I don't have (much) of a personal agenda here - I just want the rough
> edges smoothed off and a stable language.
>
>

If I recall correctly, the next thing to be implemented was support for shared libraries (dmd being able to create create position-independent code ("PIC")).

Cheers,
- Daniel

On 2011-02-20 20:21:20 -0500, Graham St Jack <Graham.StJack@internode.on.net> said:

> In particular, are there any plans to re-examine the tail-const issue in light of the compiler patch proposed by Michel Fortin in his post: "const(Object)ref is here!" back in December?

Note that there's now a pull request for that:
<https://github.com/D-Programming-Language/dmd/pull/3>

And if someone wants to test it, just download and compile the const-object-ref branch of my dmd fork:
<https://github.com/michelf/dmd/tree/const-object-ref>

I'm currently waiting for feedback from Walter about this (and possibly others who dare to test it before it's in the mainline) before putting more work on it.


-- 
Michel Fortin
michel.fortin@michelf.com
http://michelf.com/

On 18.02.2011 11:18, Walter Bright wrote:
> Now with 64 bit Linux support! (Though expect problems with it, it's
> brand new.)
>
>
> http://www.digitalmars.com/d/1.0/changelog.html
> http://ftp.digitalmars.com/dmd.1.067.zip
>
> http://www.digitalmars.com/d/2.0/changelog.html
> http://ftp.digitalmars.com/dmd.2.052.zip

Nice release in theorie but since i did not get the time to test the beta it seems some regressions made it into the release that rendered my codebase unbuildable...

The problem is that i cannot reduce it properly. (win32, dmd 2.052)

1) Without changing anything suddenly i get linker errors. I am building an executable linking in a static lib that contains some methods using std.random.uniform. When i now try to build the executable the linker complains about std.random.uniform not being found. What the heck ? The whole rest of phobos is there and this is missing ??

2) This one is really weird. After removing all the std.random.uniform crap from above it compiles and links but crashes right in the beginning befor even entering my main method. This just happens in debug builds. Funny thing is that this is not due to some unittest of mine. And correct me if i am wrong but phobos is shipped without unittests either, right ?

Any help is welcome.
Stephan