Re: Release D 2.067.0
On Wednesday, 25 March 2015 at 02:53:02 UTC, Rikki Cattermole wrote: a) A global variable that is only read before init of runtime b) CLI args c) CLI variables So, wheres d? Configure by function call. I think I should get more involved with druntime development.. You need to configure the runtime before starting it, hence it's not possible to do this as function call from your program.
Re: Release D 2.067.0
On Tuesday, 24 March 2015 at 17:08:03 UTC, Martin Nowak wrote: Glad to announce D 2.067.0. See the changelog for more details. http://dlang.org/changelog.html I don't see any mention of DIP25 here (Sealed references - return ref arguments etc.). Was it implemented and included in this release?
Re: Release D 2.067.0
On Wednesday, 25 March 2015 at 02:02:50 UTC, Paul O'Neil wrote: I have been eagerly awaiting this release for a while - especially for std.experimental.logger! let me know how you like it! I always need feedback on it
Re: 2nd London D Programmers Meetup - Robot Tank Battle Tournament
On Wed, 2015-03-25 at 11:25 +, wobbles via Digitalmars-d-announce wrote: On Tuesday, 24 March 2015 at 23:32:38 UTC, Kingsley wrote: Here are the details - spread the word: http://www.meetup.com/London-D-Programmers/events/220610394/ thanks --Kingsley Thanks for all who came to the D meetup. The champion tank of the evening goes to runaway.d by Justin Priya which defeated all challengers swiftly and in style :) Looking forward to the next meetup. Any videos of the fights? (Or were they all robot fights?) The activity was captured by the good folk of Skills Matter. It is worth noting the name of the winning tank exemplified it's strategy. It can be characterized by a quote from Monty Python and the Holy Grail: run away, run away. Whilst there, I didn't get around to writing a tank strategy, I spent too long looking at, and analysing, Kingsley's little framework – oh and chatting with Laeeth about D, Go, computational finance, etc. Kingsley's code is (mostly) great; hopefully I and others can help evolve this via pull requests, to be something we can put before CAS and others for inclusion in Key Stage 3 and 4 educational materials. Long explanation of new UK computing education system elided. This would be a great way of getting young people interested in native code after Scratch and Python. D and Java would be a good combination. -- 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: DlangUI
On Tuesday, 20 May 2014 at 18:13:36 UTC, Vadim Lopatin wrote: Hello! I would like to announce my project, DlangUI library - cross-platform GUI for D. https://github.com/buggins/dlangui License: Boost License 1.0 Native library written in D (not a wrapper to other GUI library) - easy to extend. As a backend, uses SDL2 on any platform, Win32 API on Windows, XCB on Linux. Other backends can be added easy. Tested on Windows and Linux. Supports hardware acceleration - drawing using OpenGL when built with version=USE_OPENGL. Unicode support. Internationalization support. Uses Win32 API fonts on Windows, and FreeType on other platforms. Same look and feel can be achieved on all platforms. Flexible look and feel - themes and styles. API is a bit similar to Android UI. Flexible layout, support of different screen DPI, scaling. Uses two phase layout like in Android. Supports drawable resources in .png and .jpeg, nine-patch pngs and state drawables like in Android. Single threaded. Use other threads for performing slow tasks. Mouse oriented. DlangUI review and small tutorial is published on Habrahabr - popular russian IT resource (in Russian) http://habrahabr.ru/post/253923/
Re: Berlin D Meetup March 2015
Quick report : it has happened and it was pretty intense :) Martin Nowak has given a great talk explaining D garbage collector and recent improvements to it. I presume some of that material will be present in his DConf talk too - looking forward to hearing it again. Getting everything right straight after the work day wasn't easy :)
Re: 2nd London D Programmers Meetup - Robot Tank Battle Tournament
On 25 Mar 2015 12:15, Russel Winder via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On Wed, 2015-03-25 at 11:25 +, wobbles via Digitalmars-d-announce wrote: On Tuesday, 24 March 2015 at 23:32:38 UTC, Kingsley wrote: Here are the details - spread the word: http://www.meetup.com/London-D-Programmers/events/220610394/ thanks --Kingsley Thanks for all who came to the D meetup. The champion tank of the evening goes to runaway.d by Justin Priya which defeated all challengers swiftly and in style :) Looking forward to the next meetup. Any videos of the fights? (Or were they all robot fights?) The activity was captured by the good folk of Skills Matter. It is worth noting the name of the winning tank exemplified it's strategy. It can be characterized by a quote from Monty Python and the Holy Grail: run away, run away. Whilst there, I didn't get around to writing a tank strategy, I spent too long looking at, and analysing, Kingsley's little framework – oh and chatting with Laeeth about D, Go, computational finance, etc. Kingsley's code is (mostly) great; hopefully I and others can help evolve this via pull requests, to be something we can put before CAS and others for inclusion in Key Stage 3 and 4 educational materials. Long explanation of new UK computing education system elided. This would be a great way of getting young people interested in native code after Scratch and Python. D and Java would be a good combination. Great stuff. I would have tried to come up, but with moving home and all... Vacated the flat this morning. :-o Iain
Re: Release D 2.067.0
On Tuesday, 24 March 2015 at 23:00:56 UTC, Mathias Lang wrote: Congrats to everyone involved ! A special thanks to Martin, that helped a lot to get Vibe.d ready for 2.067, and reverted the problematic changes when we realize it wasn't gonna cut it. What were the reverted changes?
Re: DTanks Alpha
On Tue, 2015-03-24 at 23:37 +, Kingsley via Digitalmars-d-announce wrote: On Saturday, 21 March 2015 at 15:57:54 UTC, Dan Olson wrote: Kingsley kingsley.hendric...@gmail.com writes: In preparation for the London D meetup I have got the DTanks robot battle framework into the first alpha release state - good enough to use at the meetup anyway. https://github.com/masterthought/dtanks And an excellent framework it is too. I hope to be able to put some programming effort towards this to help make it even better. Actually I am wondering if we can put the framework skeleton to a constructive rather than destructive purpose. --K DTanks looks cool! I am going to have to try it. Brings back memories. I got hooked on the Apple ][ version (http://corewar.co.uk/robotwar/) back in the 80's and started a version for the Amiga called Tonks but it never got off the drawing board. I've always loved this game concept. Even did a version to run each tank on a node of an Intel Hypercube as a school project. Cool - feel free to give me any feedback. At the London D programmers meetup we had a tank tournament which was great fun. Some of the guys who came had not done D before - they were Scala / Java guys - but really enjoyed playing with D by way of the tanks game. Great fun was had by all there. Thanks to Kingsley for organizing this, and perhaps more importantly, getting the framework together. An interesting point was made by some there: this looks very like Java coding. Laeeth and I both agreed, saying that we felt Kingsley background in Java was being reflected a little in the look and feel of the D code, that if a C++ programmer had written it most likely the code would have had a C++ feel to it. Much of this is about spacing, identifier structure and things like that – relatively trivial stuff in the main. The question us then is this fine ( that D code can have a Java or C++ feel) or should there always be a D feel to all D code? There should be a video of the tournament emerging at some point from SkillsMatter who sponsor the meetup as they filmed it. The video may not reflect quite as much of the fun that was had! -- 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: Release D 2.067.0
On Tuesday, 24 March 2015 at 17:08:03 UTC, Martin Nowak wrote: Glad to announce D 2.067.0. This release comes with many improvements. The GC is a lot faster for most use-cases, we have improved C++ interoperability and fixed plenty of bugs. -Martin Congratulations!!!
Re: Release D 2.067.0
On 3/24/15, Martin Nowak via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: Glad to announce D 2.067.0. Great work! It's amazing seeing how much work you guys are putting in and making D better with each new release.
Re: Digger 1.1
On Wednesday, 25 March 2015 at 20:01:43 UTC, Robert M. Münch wrote: On 2015-03-19 16:59:34 +, Vladimir Panteleev said: Hmm... Does it happen with a fresh Digger install? Just tried a fresh installed. With this I could build Digger from Git without any problems. Now trying to build 2.067 with it. OK, let me know. Might be better to take this discussion to a GitHub issue. https://github.com/CyberShadow/Digger/issues What is your core.autocrlf set to? How can I find this out? git config core.autocrlf
Re: vibe.d 0.7.23 has been released
On Wednesday, 25 March 2015 at 21:37:09 UTC, Sönke Ludwig wrote: This release adds support for the just released DMD 2.067.0 frontend. There are also some preparatory changes in vibe.core.sync (TaskMutex etc.) for planned nothrow related changes to D's mutexes and object monitors. These changes lead to a changed behavior when TaskMutex'es are mixed with the Task.interrupt() functionality. If your code uses both, please have a look at the change log for more details. Other notable changes: - Defining either of VibeDefaultMain or VibeCustomMain is now required. VibeCustomMain will be removed and made the default behavior in one of the future releases (instead of the current default, VibeDefaultMain). - The REST interface generator now accepts @queryParam and @bodyParam annotations to customize how parameters are mapped to the REST protocol. - The serialization framework now supports policy based customization. This allows to configure the serialized representation of a type without touching its definition. - The Diet template parser has received a number of fixes and now supports prepend/default mode for blocks, as well treating lines starting with as plaintext (for inline HTML lines) The full list of changes/fixes can be found at http://vibed.org/blog/posts/vibe-release-0.7.23 Homepage: http://vibed.org/ DUB package: http://code.dlang.org/packages/vibe-d GitHub: https://github.com/rejectedsoftware/vibe.d Thank you for amazing work!
vibe.d 0.7.23 has been released
This release adds support for the just released DMD 2.067.0 frontend. There are also some preparatory changes in vibe.core.sync (TaskMutex etc.) for planned nothrow related changes to D's mutexes and object monitors. These changes lead to a changed behavior when TaskMutex'es are mixed with the Task.interrupt() functionality. If your code uses both, please have a look at the change log for more details. Other notable changes: - Defining either of VibeDefaultMain or VibeCustomMain is now required. VibeCustomMain will be removed and made the default behavior in one of the future releases (instead of the current default, VibeDefaultMain). - The REST interface generator now accepts @queryParam and @bodyParam annotations to customize how parameters are mapped to the REST protocol. - The serialization framework now supports policy based customization. This allows to configure the serialized representation of a type without touching its definition. - The Diet template parser has received a number of fixes and now supports prepend/default mode for blocks, as well treating lines starting with as plaintext (for inline HTML lines) The full list of changes/fixes can be found at http://vibed.org/blog/posts/vibe-release-0.7.23 Homepage: http://vibed.org/ DUB package: http://code.dlang.org/packages/vibe-d GitHub: https://github.com/rejectedsoftware/vibe.d
Re: Release D 2.067.0
On 3/25/15 12:39 PM, Andrei Alexandrescu wrote: On 3/24/15 10:07 AM, Martin Nowak wrote: Glad to announce D 2.067.0. Spreading the news: [snip] Nice, we seem to be on HackerNews' front page: https://news.ycombinator.com/ Andrei
Gary Willoughby: Why Go's design is a disservice to intelligent programmers
https://www.reddit.com/r/programming/comments/30ad8b/why_gos_design_is_a_disservice_to_intelligent/ Andrei
Re: Release D 2.067.0
On 3/25/15 1:32 PM, Andrei Alexandrescu wrote: On 3/25/15 12:39 PM, Andrei Alexandrescu wrote: On 3/24/15 10:07 AM, Martin Nowak wrote: Glad to announce D 2.067.0. Spreading the news: [snip] Nice, we seem to be on HackerNews' front page: https://news.ycombinator.com/ And apparently we did something wrong - somehow we fell in minutes from position 11 to position 41. -- Andrei
Re: Release D 2.067.0
On Tuesday, 24 March 2015 at 17:08:03 UTC, Martin Nowak wrote: Glad to announce D 2.067.0. This release comes with many improvements. The GC is a lot faster for most use-cases, we have improved C++ interoperability and fixed plenty of bugs. See the changelog for more details. http://dlang.org/changelog.html Download pages and documentation will be updated within the next few hours. http://downloads.dlang.org/releases/2.x/2.067.0/ http://ftp.digitalmars.com/ Until the binaries are mirrored to the official site, you can get them here. https://dlang.dawg.eu/downloads/dmd.2.067.0/ -Martin from the reddit thread: Anyone know if there's been any comparisons of different heapSizeFactor values? Primarly, compared to the default 2, 1.5 or 1.618. has anyone working on the GC actually done any comparisons of the new options?
Re: Digger 1.1
On 2015-03-19 16:59:34 +, Vladimir Panteleev said: Hmm... Does it happen with a fresh Digger install? Just tried a fresh installed. With this I could build Digger from Git without any problems. Now trying to build 2.067 with it. What is your core.autocrlf set to? How can I find this out? -- Robert M. Münch http://www.saphirion.com smarter | better | faster
Re: vibe.d 0.7.23 has been released
2015-03-25 22:37 GMT+01:00 Sönke Ludwig digitalmars-d-announce@puremagic.com: This release adds support for the just released DMD 2.067.0 frontend. There are also some preparatory changes in vibe.core.sync (TaskMutex etc.) for planned nothrow related changes to D's mutexes and object monitors. These changes lead to a changed behavior when TaskMutex'es are mixed with the Task.interrupt() functionality. If your code uses both, please have a look at the change log for more details. Thanks for all the time and work you put on Vibe :)
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
Ola Fosheim Grøstad: Downplaying other languages makes the D crowd look desperate... That kind of articles are bad for the image of the D community (and the D code shown in that article is not the best). Bye, bearophile
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On 3/25/15 2:55 PM, Mathias Lang via Digitalmars-d-announce wrote: I just wish D examples didn't include string lambdas. There was an initiative to just change them everywhere, seems to have petered out. Just do it. -- Andrei
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Wednesday, 25 March 2015 at 22:30:15 UTC, Ola Fosheim Grøstad wrote: Go has stability, is production ready and has an ecosystem with commercial value. You could say the same things about Cobol or PHP, but that doesn't mean the languages themselves should be free from criticism. My opinion of Go was very much consistent with the article. It doesn't mean much to me to have a stable language that I don't want to use. His points are valid.
Re: vibe.d 0.7.23 has been released
Am 25.03.2015 um 22:57 schrieb Mathias Lang via Digitalmars-d-announce: 2015-03-25 22:37 GMT+01:00 Sönke Ludwig digitalmars-d-announce@puremagic.com mailto:digitalmars-d-announce@puremagic.com: This release adds support for the just released DMD 2.067.0 frontend. There are also some preparatory changes in vibe.core.sync (TaskMutex etc.) for planned nothrow related changes to D's mutexes and object monitors. These changes lead to a changed behavior when TaskMutex'es are mixed with the Task.interrupt() functionality. If your code uses both, please have a look at the change log for more details. Thanks for all the time and work you put on Vibe :) Thanks for your considerable contributions, too (much of the 2.067 preparation and many REST improvements have been done by Mathias)!
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Wednesday, 25 March 2015 at 21:00:37 UTC, Andrei Alexandrescu wrote: https://www.reddit.com/r/programming/comments/30ad8b/why_gos_design_is_a_disservice_to_intelligent/ Andrei Downplaying other languages makes the D crowd look desperate... Go has stability, is production ready and has an ecosystem with commercial value. D lacks all of these atm...
Re: vibe.d 0.7.23 has been released
Any news on reducing memory usage during Diet template compilation? This one of the main reasons for me to discourage people from using vibe.d right now.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Wednesday, 25 March 2015 at 23:00:32 UTC, bearophile wrote: Ola Fosheim Grøstad: Downplaying other languages makes the D crowd look desperate... That kind of articles are bad for the image of the D community (and the D code shown in that article is not the best). Bye, bearophile +1 but his points about go really are right.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Wednesday, 25 March 2015 at 21:00:37 UTC, Andrei Alexandrescu wrote: https://www.reddit.com/r/programming/comments/30ad8b/why_gos_design_is_a_disservice_to_intelligent/ Andrei As I know Gary is sometimes (often?) on these forums I'll post some critique here. Misrepresenting Go in a comparison with D doesn't reflect well on the D community, so please have a look at the following issues: In the first code example, the Go version returns 1 on failure and 0 on success, while the D version always returns 0. Also, the Go version correctly uses stderr for error messages while the D version uses stdout for everything. In the second example maybe you should print four lists to be equivalent of the Go code. I think it's misrepresentative to shorten the D example by making it do less work. auto text = source.byLine.join.to!(string); This is not safe as byLine reuses the same buffer for every line. It may or may not work depending on join's implementation. Also, it's idiomatic to omit parantheses when a template argument list consists of a single token: source.byLine.join.to!string; With all that said, I honestly think Go’s design a disservice to intelligent programmers. s/design a disservice/design is a disservice/ From my experience of using Go it’s just too simple to create useful abstractions. This sentence is ambiguous and could be taken to mean it's really simple to create useful abstractions in Go. The intended meaning is obvious with context, but it threw me off for a second... I guess by now Go programmers reading this will be frothing at the mouth shouting “Your doing it wrong!”. s/your/you're/ That could be misconstrued as a jab at the intelligence of Go programmers, which I don't think serves your cause. Well, there is another way of implementing generic functions and data types, and that is to completely break the type system! Didn't you just say there was simply no way around it? I know object-oriented programming is no silver bullet but it would of been nice to be able to abstract details away into types and provide better encapsulation. s/would of/would have/ Also, this statement just begs for responses pointing to Go's OOP features. It has both user-defined types and encapsulation features.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Thursday, 26 March 2015 at 00:19:44 UTC, Jakob Ovrum wrote: As I know Gary is sometimes (often?) on these forums I'll post some critique here. Misrepresenting Go in a comparison with D doesn't reflect well on the D community, so please have a look at the following issues: You describe these as issues forming part of a critique and suggesting the substance of what he wrote is wrong, but are these substantive in the context of a quick blog post (where it is more important to say something generative than to be perfect in its expression). I don't claim to know Go, but is his basic point off the mark? In the first code example, the Go version returns 1 on failure and 0 on success, while the D version always returns 0. Also, the Go version correctly uses stderr for error messages while the D version uses stdout for everything. stderr.writeln(text); return 1; correctness is important, but does this change much? In the second example maybe you should print four lists to be equivalent of the Go code. I think it's misrepresentative to shorten the D example by making it do less work. surely people can see beyond a difference of three lines ? would this change his point? auto text = source.byLine.join.to!(string); This is not safe as byLine reuses the same buffer for every line. It may or may not work depending on join's implementation. Also, it's idiomatic to omit parantheses when a template argument list consists of a single token: source.byLine.join.to!string; fair point if true (I will let others who know better say whether .array. or something is needed). With all that said, I honestly think Go’s design a disservice to intelligent programmers. s/design a disservice/design is a disservice/ What he wrote is correct English, and he is an Englishman living in England. I guess by now Go programmers reading this will be frothing at the mouth shouting “Your doing it wrong!”. That could be misconstrued as a jab at the intelligence of Go programmers, which I don't think serves your cause. Again, nobody English would think this was more than mildly humorous (and by no means insulting). To suggest somebody is rabid is not to insult their intelligence, but merely to tease them about their likely strong emotional reaction. But what is one to do when making the trade-off between being blandly corporate and acceptable to everyone, versus writing with some character and spirit and offending the sensitive. It's a personal choice, but not easy to criticize another for theirs. I personally find the world too bland these days. One cannot police the forms of expression of people who do not speak for a community or claim to be acting as such (apologies if I am mistaken and he does have an official position within D). And perhaps one ought not to try. Laeeth.
Re: Release D 2.067.0
On Tuesday, 24 March 2015 at 18:18:44 UTC, Martin Nowak wrote: [snip] What I'm regretting more, is that I have to run after every contributor, bugging them 3 times to write a single changelog line. One way to improve this would be to have changelogs in the dmd/druntime/phobos repo and make the entries part of the pull requests. That's a good idea. Maybe use separate files for each changelog entry (which are then combined into into the actual changelog by the dlang.org makefile). Then there wouldn't be merge conflicts with basically every pull request. Something like: changelog/v[upcoming dmd version]-[bugzilla issue number]-[github username].log (e.g., changelog/v2.068.0-314-9rnsr.log)
Re: Release D 2.067.0
On Thursday, 26 March 2015 at 01:44:44 UTC, Brad Anderson wrote: That's a good idea. Maybe use separate files for each changelog entry (which are then combined into into the actual changelog by the dlang.org makefile). Then there wouldn't be merge conflicts with basically every pull request. [snip] Just noticed you mention merge=union. That's a neat feature. I'd never seen it before.
Re: Deadcode on github
On Tuesday, 17 March 2015 at 12:39:00 UTC, Jonas Drewsen wrote: Definitely. I've now made a branch linux on github where linux compiles and links successfully and that also includes steps towards abstracting stuff. Thanks a lot. Sadly this branch still doesn't seem to compile because of other issues (that don't seem to be related to platform portability). I think I will wait for some tagged release before rushing into experiments :)
Re: Release D 2.067.0
On 3/25/2015 1:07 AM, thedeemon wrote: I don't see any mention of DIP25 here (Sealed references - return ref arguments etc.). Was it implemented and included in this release? Yes.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Thursday, 26 March 2015 at 02:04:26 UTC, Laeeth Isharc wrote: You describe these as issues forming part of a critique and suggesting the substance of what he wrote is wrong, but are these substantive in the context of a quick blog post (where it is more important to say something generative than to be perfect in its expression). The comparison, as-is, is unfair. He writes a long-winded Go snippet (which it turns out is completely unrepresentative of an idiomatic Go solution[1]) then counters it with a short D solution that deceptively does less work. I did not mean to suggest his overall claims are wrong; I strongly agree with him on his main points. The problem is that he's using faulty data to reach that conclusion. I don't claim to know Go, but is his basic point off the mark? At the very least, he's completely misrepresented the difference with the unnaturally long Go snippet[1] and the incomplete D snippet. stderr.writeln(text); return 1; correctness is important, but does this change much? The size of the code is an essential point in this post. It's probably safe to say most readers can't spot the difference in semantics, which makes Go look disproportionally verbose. In the second example maybe you should print four lists to be equivalent of the Go code. I think it's misrepresentative to shorten the D example by making it do less work. surely people can see beyond a difference of three lines ? would this change his point? I think it makes a big difference visually. fair point if true (I will let others who know better say whether .array. or something is needed). join and array on byLine both suffer the same problem. Using joiner instead of join would fix it and still allow it to forego copying each line. What he wrote is correct English, and he is an Englishman living in England. Great. Again, nobody English would think this was more than mildly humorous (and by no means insulting). To suggest somebody is rabid is not to insult their intelligence, but merely to tease them about their likely strong emotional reaction. I wasn't referring to that, I was referring to the grammatical error in the quote. But what is one to do when making the trade-off between being blandly corporate and acceptable to everyone, versus writing with some character and spirit and offending the sensitive. It's a personal choice, but not easy to criticize another for theirs. I personally find the world too bland these days. One cannot police the forms of expression of people who do not speak for a community or claim to be acting as such (apologies if I am mistaken and he does have an official position within D). And perhaps one ought not to try. I intentionally did not want to criticize his post as a whole, just the methodology employed. The post has been met with a lot of scorn on Reddit, and I think it would help D's case to get the facts right. [1] https://www.reddit.com/r/programming/comments/30ad8b/why_gos_design_is_a_disservice_to_intelligent/cpqpfjx
Re: 2nd London D Programmers Meetup - Robot Tank Battle Tournament
On Tuesday, 24 March 2015 at 23:32:38 UTC, Kingsley wrote: Here are the details - spread the word: http://www.meetup.com/London-D-Programmers/events/220610394/ thanks --Kingsley Thanks for all who came to the D meetup. The champion tank of the evening goes to runaway.d by Justin Priya which defeated all challengers swiftly and in style :) Looking forward to the next meetup. Any videos of the fights? (Or were they all robot fights?)
Re: Release D 2.067.0
On Tue, 24 Mar 2015 18:07:42 +0100 Martin Nowak via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: Glad to announce D 2.067.0. This release comes with many improvements. The GC is a lot faster for most use-cases, we have improved C++ interoperability and fixed plenty of bugs. See the changelog for more details. http://dlang.org/changelog.html Download pages and documentation will be updated within the next few hours. http://downloads.dlang.org/releases/2.x/2.067.0/ http://ftp.digitalmars.com/ Until the binaries are mirrored to the official site, you can get them here. https://dlang.dawg.eu/downloads/dmd.2.067.0/ -Martin Thanks for your work. One minor issue in changelog DMD Compiler enhancements 14. Bugzilla 13388: accept '@' before 'nothrow' and 'pure' I think this shoud not be here
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
I just wish D examples didn't include string lambdas. 2015-03-25 22:00 GMT+01:00 Andrei Alexandrescu via Digitalmars-d-announce digitalmars-d-announce@puremagic.com: https://www.reddit.com/r/programming/comments/30ad8b/why_gos_design_is_a_ disservice_to_intelligent/ Andrei
Re: vibe.d 0.7.23 has been released
Am 25.03.2015 um 23:30 schrieb George Sapkin: Any news on reducing memory usage during Diet template compilation? This one of the main reasons for me to discourage people from using vibe.d right now. Martin Nowak has started to work on a new CTFE interpreter for DMD, which should finally fix these issues. I have tried long and hard to get memory use of the Diet compiler down in the past (which is partially why the code for it looks so ugly), but ultimately the compiler has to be fixed.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Wednesday, 25 March 2015 at 23:00:32 UTC, bearophile wrote: Ola Fosheim Grøstad: Downplaying other languages makes the D crowd look desperate... That kind of articles are bad for the image of the D community (and the D code shown in that article is not the best). Bye, bearophile I don't know about that... I too think that maybe it was a clumsy way of doing it but I'm not sure that we would have had such critics if Python (eg.) had been choosen to write the examples, even with not very pythonic code. Maybe it should have been backed up with another language not to put the comparison on D alone. Bad publicity is better than no publicity in many cases. There's no reason why this couldn't play out right in the end.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Thursday, 26 March 2015 at 02:34:04 UTC, Jakob Ovrum wrote: On Thursday, 26 March 2015 at 02:04:26 UTC, Laeeth Isharc wrote: [snip] It would have been better if several languages were used in comparison to Go. Overall the blog post is a bit immature with little rigor and too much emotion. The code comparisons that aren't idiomatic for either language nor behaviorally equivalent. It reads like a D-zealot had decided to write this blog before they even clicked the download link for the Go compiler. And so, their experience was never going to be anything but negative. That said, Go is unpleasant and probably the most boring language I've had to write code in. bye, lobo
Re: DlangUI
On Wednesday, 25 March 2015 at 14:14:13 UTC, Vadim Lopatin wrote: On Tuesday, 20 May 2014 at 18:13:36 UTC, Vadim Lopatin wrote: Hello! I would like to announce my project, DlangUI library - cross-platform GUI for D. https://github.com/buggins/dlangui License: Boost License 1.0 Native library written in D (not a wrapper to other GUI library) - easy to extend. As a backend, uses SDL2 on any platform, Win32 API on Windows, XCB on Linux. Other backends can be added easy. Tested on Windows and Linux. Supports hardware acceleration - drawing using OpenGL when built with version=USE_OPENGL. Unicode support. Internationalization support. Uses Win32 API fonts on Windows, and FreeType on other platforms. Same look and feel can be achieved on all platforms. Flexible look and feel - themes and styles. API is a bit similar to Android UI. Flexible layout, support of different screen DPI, scaling. Uses two phase layout like in Android. Supports drawable resources in .png and .jpeg, nine-patch pngs and state drawables like in Android. Single threaded. Use other threads for performing slow tasks. Mouse oriented. DlangUI review and small tutorial is published on Habrahabr - popular russian IT resource (in Russian) http://habrahabr.ru/post/253923/ It does not looks like something with a `soul`. It looks like a copy of something that already exists.
