Re: GSOC 2015 - GNU dmd
On Wednesday, 4 March 2015 at 22:08:44 UTC, Walter Bright wrote: On 3/3/2015 1:15 PM, notna wrote: not sure if someone should inform them about the DMD name clash... or just enjoy the popularity ;) http://www.gnu.org/software/dmd I sent them a note. I'd suggest Daemon Hurder or dhurd.
Re: dfmt 0.1.0
On Thursday, 5 March 2015 at 09:02:25 UTC, Russel Winder wrote: Since using Go and working on a couple of fairly old C++ codebases, all of which use tab for indent, I have come to rather like it. You probably feel that way because tabs are better. dfmt only defaults to spaces because that's what's in the Phobos style guide.
Re: dfmt 0.1.0
On Thu, 2015-03-05 at 08:17 +0100, Jacob Carlborg via Digitalmars-d-announce wrote: On 2015-03-04 16:26, Russel Winder via Digitalmars-d-announce wrote: There ought to be for the compiler/formatter toolchain otherwise there will be problems. And if there is a D parser as library and it works why would anyone want another parser? The DMD front end is not really designed to be used as a library for tooling. It would be good if the D implemented D parser were though. Parsing to create an AST is needed for many things. If each tool in the tool chain implements it's own… it just seems wrong. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Re: dfmt 0.1.0
On Wed, 2015-03-04 at 21:22 +, Brian Schott via Digitalmars-d-announce wrote: […] That means that the Emacs plugin needs to start it automatically. Is this something on your todo list, or do you need a pull request? Implementing a separate parser based on the language spec has helped to find problems with the language spec. Having One True Implementation can lead to problems as well. https://issues.dlang.org/show_bug.cgi?id=10233 I just wonder if it is wise to have a single two chain with two distinct parsers which have separate lifecycles? (*) The exception is of course Phobos style which I find so annoying I can't read code formatted that way. By default dfmt tries to output Phobos style code. There is an option to use a different brace style and another one to use tabs. Since using Go and working on a couple of fairly old C++ codebases, all of which use tab for indent, I have come to rather like it. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Re: This Week in D #7 - summary of reference counting discussion
It was very cool from the very beginning but when all new ref counting discussions happened and I didn't have time to follow - that was the moment of true appreciation of This Week in D. Thank you, Adam.
Re: dfmt 0.1.0
Jacob Carlborg wrote in message news:md8vu6$hc1$1...@digitalmars.com... The DMD front end is not really designed to be used as a library for tooling. It isn't, but it's slowly getting better. eg You can now build the lexer as a library without pulling everything else in. It's quite possible that in a couple of years it will be in a state where it's reasonable to build tools on top of it.
