Re: Visual D 0.47.0 released
On Sunday, 24 June 2018 at 13:08:53 UTC, Rainer Schuetze wrote: Hi, a new release of Visual D has just been uploaded. Major changes are * improved Visual C++ project integration: better dependencies, automatic libraries, name demangling * new project wizard * mago debugger: show vtable, dynamic type of interfaces, symbol names of pointer address See http://rainers.github.io/visuald/visuald/VersionHistory.html for the full version history. Visual D is a Visual Studio extension that adds D language support to VS2008-2017. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. An installer can be found at http://rainers.github.io/visuald/visuald/StartPage.html Happy coding, Rainer It will really be nice if visual D can come to visual Studio code. It is a beautiful nice work. Pls can we have it in visual Studio code? Pls...
Re: autowrap v0.0.1 - Automatically wrap existing D code for use in Python and Excel
Eg turn this into a function and try wrapping this instead:
auto intp = interpreter(dmdEngine());
Thanks for your help. I'm doing this in my spare time which is,
unfortunately, not much.
I did what you said
export {
auto intp = interpreter(echoEngine);
}
but when I import drepl from python idle I still can access intp.
Aedi property reader, config file readers and more.
Hi, Dlang community! Announcing aedi property reader v0.2.0, a library for reading various config files and exposing the contents as components (accessed by their path from container) that you can use in your application, without the hassle of manually reading file, then convert into D data type, check for correctness and etc. The new additions to v0.2.0: 1) Brings three more file formats: sdlang, yaml, and java property files, with all basic D scalar types and their arrays supported out of the box (if I'm missing smth, please create a issue or better a pull request :) ) 2) Brings experimental feature of reading structs and objects (with @property annotated fields) from config files (be warned, array of structs/objects not supported yet). 3) Built with allocators in mind (it still is dependent on underlying libraries used to read config files). Check out examples folder. Build and run them with a simple "dub run". Dub link: http://code.dlang.org/packages/aedi-property-reader Planned for future: 1) Extract object/struct mapper functionality in external library. 2) Figure out how to add array of structs/objects for reading. Best regards, Alexandru.
Re: Visual D 0.47.0 released
On 24/06/2018 19:56, Brian wrote: On Sunday, 24 June 2018 at 13:08:53 UTC, Rainer Schuetze wrote: Hi, a new release of Visual D has just been uploaded. Major changes are * improved Visual C++ project integration: better dependencies, automatic libraries, name demangling * new project wizard * mago debugger: show vtable, dynamic type of interfaces, symbol names of pointer address See http://rainers.github.io/visuald/visuald/VersionHistory.html for the full version history. Visual D is a Visual Studio extension that adds D language support to VS2008-2017. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. An installer can be found at http://rainers.github.io/visuald/visuald/StartPage.html Happy coding, Rainer Thanks! Can use dub.json to manager project? You can use "dub generate visuald" to generate a project and solution for Visual D.
Re: Visual D 0.47.0 released
On Sunday, 24 June 2018 at 13:08:53 UTC, Rainer Schuetze wrote: Hi, a new release of Visual D has just been uploaded. Major changes are * improved Visual C++ project integration: better dependencies, automatic libraries, name demangling * new project wizard * mago debugger: show vtable, dynamic type of interfaces, symbol names of pointer address See http://rainers.github.io/visuald/visuald/VersionHistory.html for the full version history. Visual D is a Visual Studio extension that adds D language support to VS2008-2017. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. An installer can be found at http://rainers.github.io/visuald/visuald/StartPage.html Happy coding, Rainer Thanks! Can use dub.json to manager project?
Re: Dutyl 1.5.0 released - dfmt support added
On Wednesday, 20 June 2018 at 19:08:49 UTC, Timoses wrote: Timoses wrote: Any ideas why autocompletion doesn't? Opps. I suppose One should use vim's autocomplete feature : D (i_CTRL-P) Hm, this doesn't seem to use the autocomplete feature. I've set it up so far that I can use `:DUjump` on for example std.algorithm and it'll jump right to the algorithm file. NICE! But, how to use the autocompletion feature? E.g. typing levensh and trying i_CTRL-P does not resolve to anything... How does it work??
Visual D 0.47.0 released
Hi, a new release of Visual D has just been uploaded. Major changes are * improved Visual C++ project integration: better dependencies, automatic libraries, name demangling * new project wizard * mago debugger: show vtable, dynamic type of interfaces, symbol names of pointer address See http://rainers.github.io/visuald/visuald/VersionHistory.html for the full version history. Visual D is a Visual Studio extension that adds D language support to VS2008-2017. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. An installer can be found at http://rainers.github.io/visuald/visuald/StartPage.html Happy coding, Rainer
Munich D Meetup June 2018
Our next meetup will be tomorrow June 25th. Details and RSVP at: https://www.meetup.com/de-DE/Munich-D-Programmers/events/251718757/
Re: How an Engineering Company Chose to Migrate to D
On Saturday, 23 June 2018 at 10:00:48 UTC, user1234 wrote: On Saturday, 23 June 2018 at 09:41:19 UTC, Ecstatic Coder wrote: Like everybody here, I hope that Bastiaan efforts will pay in the long term, but I'm not as optimistic as many here that this will end as a success story, as I'm not sure that his teammates will really enjoy working the automatically generated D code as much as on the original source code... Yes but their job is to make boats floating (like said Veelo at Dconf 2017, not writing compilers. Pascal lags behind and not a few, in term of expressiveness. Also transpilation of Pascal to something else is simple because no semantic is needed. Indeed, my expectation is that I don’t even need to maintain a symbol table. Stefan Koch disagrees with me though, and I’m on a quest to prove him wrong ;-)
Re: How an Engineering Company Chose to Migrate to D
On Saturday, 23 June 2018 at 09:41:19 UTC, Ecstatic Coder wrote: Where I disagree with Bastiaan is on the rejection of the Pascal language itself, as there are other open-source Pascal compilers (GNU Pascal in EP mode) which could have been used and enhanced to match the company requirements, while preserving the company future for the decades to come. Yes, it's a shame that GNU Pasal (gpc) is in the shape it is. Betting on gpc would be like betting on a dead horse. The name GNU Pascal is misleading, as gpc was never integrated with gcc. There's this thread [1] from 2004 that integration was already overdue, and that an initiative to do this in 2000 had failed. In 2006 it was apparent that gpc was falling out of the mainline [2] by failing to port to gcc 4. Quoting Wikipedia: In July 2010 a developer publicly asked opinion [3] (it vanished from the web between July/2014 and June/2015) on the future of GNU Pascal, due to developer shortage and maintenance issues as a GCC port. There was a lively discussion on the maillist [4] where the developers seemed to lean towards reimplementing in C++ with a C code generating backend. The maillist went to sleep again, and as of December 2016 no further releases or announcements about the future course of the project have been made. As you can see, I was part of that discussion [4] in which I suggested to use D instead of C++ for a reimplementation. If only they knew then what we know now. I have tried to use gpc for the SARC code base in 2006, which mostly worked except that SARC had started using Prospero extensions (without being conscious about it). EP support in gpc may also not have been complete yet, I am not sure. This made a port too costly, considering that Prospero was still working very well. In addition, the string binary compatibility would probably also have popped up, as the standard does not define a string implementation, so the binary representation of strings depends on the compiler implementation. I also was less experienced, which is why I didn't want to pick up a corroding project outside my field of expertise. IMHO, implementing a EP-to-D source code converter was probably more risky than simply extending an existing Pascal Compiler in that case. Risc is in the eye of the beholder ;-) Like everybody here, I hope that Bastiaan efforts will pay in the long term, but I'm not as optimistic as many here that this will end as a success story, as I'm not sure that his teammates will really enjoy working the automatically generated D code as much as on the original source code... We will have to see. In the meantime, I already completed automated translation of our test case of schematic types, a difficult one. I want to thank everyone for all the attention to this article and for the project in general. I'll keep you guys posted! Bastiaan. [1] https://gcc.gnu.org/ml/gcc/2004-12/msg00782.html [2] http://www.g-n-u.de/pipermail/gpc/2006-November/013950.html [3] https://web.archive.org/web/20140714170318/http://fjf.gnu.de/gpc-future.html [4] http://www.g-n-u.de/pipermail/gpc/2010-July/thread.html
