Re: D needs...
On Monday, 11 May 2015 at 11:59:02 UTC, Namespace wrote: Inspired by ponce idioms list for D I've set up something similar. There are some themes in D which come up regulary and are discussed to the vomit. If something is agreed, it gets forgotten sometimes and the theme disappears into oblivion (for a few months :P). To prevent this, I've collected some hot-discussed themes, their history and their current state. I hope this helps to avoid unnecessary discussions in the future and finally cut off these issues (either with an official decision Nope, keep as it is or with an implementation). I've tried to stay as objective as possible, but if something seems to be too subjective, please let me know, so I can fix it. http://dgame.github.io/dneeds/ Nice! Especially the discussion links. Would be good to see a final-by-default summary too.
Re: D needs...
On Tue, 12 May 2015 06:39:09 + ponce via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On Monday, 11 May 2015 at 11:59:02 UTC, Namespace wrote: Inspired by ponce idioms list for D I've set up something similar. There are some themes in D which come up regulary and are discussed to the vomit. If something is agreed, it gets forgotten sometimes and the theme disappears into oblivion (for a few months :P). To prevent this, I've collected some hot-discussed themes, their history and their current state. I hope this helps to avoid unnecessary discussions in the future and finally cut off these issues (either with an official decision Nope, keep as it is or with an implementation). I've tried to stay as objective as possible, but if something seems to be too subjective, please let me know, so I can fix it. http://dgame.github.io/dneeds/ Nice! Especially the discussion links. Would be good to see a final-by-default summary too. There would be too much discussion links ;-)
Re: D needs...
On Tuesday, 12 May 2015 at 06:39:10 UTC, ponce wrote: On Monday, 11 May 2015 at 11:59:02 UTC, Namespace wrote: Inspired by ponce idioms list for D I've set up something similar. There are some themes in D which come up regulary and are discussed to the vomit. If something is agreed, it gets forgotten sometimes and the theme disappears into oblivion (for a few months :P). To prevent this, I've collected some hot-discussed themes, their history and their current state. I hope this helps to avoid unnecessary discussions in the future and finally cut off these issues (either with an official decision Nope, keep as it is or with an implementation). I've tried to stay as objective as possible, but if something seems to be too subjective, please let me know, so I can fix it. http://dgame.github.io/dneeds/ Nice! Especially the discussion links. Would be good to see a final-by-default summary too. As you wish: http://dgame.github.io/dneeds/#final-by-default
Re: DlangIDE
On Friday, 8 May 2015 at 17:26:18 UTC, Chris wrote: On Tuesday, 10 March 2015 at 10:39:16 UTC, Vadim Lopatin wrote: On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote: Hello, I'm working on cross-platform D language IDE - DlangIDE. It's written in D using DlangUI based GUI. Project on GitHub: https://github.com/buggins/dlangide It's in alpha stage but already allows: * Open DUB based projects * Edit source files * Build and run projects using DUB * D source code syntax highlight Requires DUB for building projects. Features missing so far: * Debugging support * Code completion * Code folding * Go to definition * Smart indentation Recent changes in DlangIDE: Settings dialog added (editor settings and UI options, including options for tuning of font rendering) Dark theme implemented (available for all DlangUI apps as well) Search feature - contributed by Freakazo Best regards, Vadim Does DlangIDE offer plugin mechanisms? Would be great, if we could write plugins. Plugins are not planned in nearest future. IMHO so far it's better just to embed functionality into app.
Re: DlangIDE
On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote: Hello, I'm working on cross-platform D language IDE - DlangIDE. It's written in D using DlangUI based GUI. Project on GitHub: https://github.com/buggins/dlangide It's in alpha stage but already allows: * Open DUB based projects * Edit source files * Build and run projects using DUB * D source code syntax highlight Requires DUB for building projects. Features missing so far: * Debugging support * Code completion * Code folding * Go to definition * Smart indentation Best regards, Vadim Is DUB required to install and use the IDE?
Re: Calypso: Direct and full interfacing to C++
Well the first fully working example of a large library is finally working with Calypso. Elie has managed to get a Qt5 demo program to compile and run!! The demo is a D version of the Qt5 Widgets demo. This is a simple window with a pseudo address book app. The demo uses a D class inheriting from QWidget, calls 'super(parent)' from D code and uses the QStrings, QLabel, QLineEdit, QLayout, QGridLayout classes, among other things. You can see the code here: https://github.com/Syniurge/Calypso/blob/master/tests/calypso/qt5/qt5demo.d The demo is confirmed to work with Qt5.4 and Qt5.2.1. While this might not seem like a really big deal, please keep in mind that while compiling this demo, Calypso effectively parses and produces 692 object files, including large swathes of the C++ STL and most of the Qt library! The latest push last night also cut down on compile times quite a lot. Doing the initial compile of the example takes about 28 seconds on my mid-level Intel i5 machine, versus around 2 seconds for just the C++ version. After generating a cache file with last nights commits you can recompile the project in just 7.5 seconds...which I think is quite good for just getting things up and running :) Thanks, Kelly
Re: D needs...
On Monday, 11 May 2015 at 17:49:32 UTC, Namespace wrote: I've read DIP69 and there were a few lines about scope ref. But I'm not sure whether I understand everything correct (because there is no concrete application example for my case): will DIP69 create the possibility to pass rvalues and lvalues alike to a function without the abuse of templates? Or did I got that wrong? DIP69 is more or less dead, we're going with a variation of DIP25 (although that one still has holes). As for rvalue ref, it would enable them safely, but it is not a part of that DIP (or DIP69, AFAICS).
Re: D needs...
On Tuesday, 12 May 2015 at 09:31:13 UTC, Marc Schütz wrote: On Monday, 11 May 2015 at 17:49:32 UTC, Namespace wrote: I've read DIP69 and there were a few lines about scope ref. But I'm not sure whether I understand everything correct (because there is no concrete application example for my case): will DIP69 create the possibility to pass rvalues and lvalues alike to a function without the abuse of templates? Or did I got that wrong? DIP69 is more or less dead, we're going with a variation of DIP25 (although that one still has holes). As for rvalue ref, it would enable them safely, but it is not a part of that DIP (or DIP69, AFAICS). And I thought for a moment, we have a solution in sight... :)
Re: DOtherSide: QML bindings for both D and Nim
On Monday, 11 May 2015 at 05:46:58 UTC, Suliman wrote: Could you add examples of usage this binding on Windows please. This is part of the overall goal to write some basic documentation for D (i've already done it for Nim). However if you're familiar with the basic cmake workflow you should more or less set. The first step is building the libDOtherSide c++ library and then your d application. Take a look at the examples for the usage and how to link the libdqml static library
Re: DWT 64bit support
On Sunday, 10 May 2015 at 16:11:41 UTC, Jacob Carlborg wrote: I would like to announce that DWT recently got support for 64bit, both on Linux and Windows. Compiling for 32bit COFF should also work on Windows. All this work was done by kntroh and Jesse Phillips, thank you very much. This is wonderful news.
Re: This Week in D 16: microcontroller, andoid, std.allocator, lazy import trick
On Monday, 11 May 2015 at 03:09:53 UTC, Adam D. Ruppe wrote: http://arsdnet.net/this-week-in-d/may-10.html https://twitter.com/adamdruppe/status/597598994227924992 The tip could probably use a rewrite in editing, but I'm out of time again tonight and I hope I got the point across anyway. As someone who really likes distributing single-file libraries when possible, the lazy import has given me some cool interop things without compromising my preferred distribution strategy. I think producing this news bulletin is the single best thing you guys have done recently for the D programming language. It makes it easy for someone like myself that is still learning the language (4 years now) and is wanting to know more about what is happening but don't know where to start. Unfortunately I don't use D in my job daily so it's nice to get a new feed with the highlights on what is happening. Anyway I just wanted to let you know that I appreciate all your hard work on this Adam and you definitely have a fan. I am looking forward to reading next weeks post.
Re: D needs...
On 5/12/15 3:09 AM, Namespace wrote: On Tuesday, 12 May 2015 at 09:31:13 UTC, Marc Schütz wrote: On Monday, 11 May 2015 at 17:49:32 UTC, Namespace wrote: I've read DIP69 and there were a few lines about scope ref. But I'm not sure whether I understand everything correct (because there is no concrete application example for my case): will DIP69 create the possibility to pass rvalues and lvalues alike to a function without the abuse of templates? Or did I got that wrong? DIP69 is more or less dead, we're going with a variation of DIP25 (although that one still has holes). As for rvalue ref, it would enable them safely, but it is not a part of that DIP (or DIP69, AFAICS). And I thought for a moment, we have a solution in sight... :) Knee-jerk response: if no return attribute on a function it should be safe to bind rvalues to ref parameters. Of course that's impractical as a default so explicit auto ref would be needed. -- Andrei
Re: D needs...
Knee-jerk response: if no return attribute on a function it should be safe to bind rvalues to ref parameters. Of course that's impractical as a default so explicit auto ref would be needed. -- Andrei yay, I'm glad to hear that. :)
