Re: Mono-D v2.4.9 - Parser fixes
Alexander Bothe i...@alexanderbothe.com wrote in message news:clmyaoqgxizsicodj...@forum.dlang.org... Hi everyone, just wanted to announce a further small version bump of Mono-D. And yeah, despite my 2 week-break, development still continues! Cheers, Alex Great. Any news of an integrated debugger... :-) -=mike=-
Re: Dutyl - a Vim plugin for running D tools
On Thursday, 14 August 2014 at 22:20:52 UTC, Idan Arye wrote: GitHub repo: https://github.com/idanarye/vim-dutyl vim.org page: http://www.vim.org/scripts/script.php?script_id=5003 The main problem with my Vim plugin for DCD(placed inside the DCD repo) is the need to set the import paths manually. It was a manual task that the user had to do: DCD doesn't know the import path the current project is using. Vim doesn't know either. Luckily - DUB knows. So instead of separate Vim plugins for different tools, each operating it's own tool alone, I wanted to create one plugin that'll operate both DUB and DCD - one that can get the list of import modules from DUB and send it to DCD. That's how Dutyl was born. Currently, Dutyl's only features are using DCD for autocompletion and for DDocs, but it has a module system that allows it to add other tools, either to get more functionality or to get backup for features that some tools can't support for specific projects. Like dependency injection but with a real usecase: for projects that don't use DUB, Dutyl can back up to a manually written list of import paths saved in a hidden file in the project's dir. I'm open for suggestions for other tools and features to add to Dutyl(write them here, or preferably open GitHub issues with them) How does dutyl know where to look for dub.json? It doesn't seem to find it on my system.
Re: DUB 0.9.22 released
On Mon, Sep 22, 2014 at 21:04:24 +, tn via Digitalmars-d-announce wrote:
What is the recommended way of versioning bindings? If the
binding of the target library 1.2.3 is versioned as 1.2.3 and a
bug is fixed in the binding (no change in the target library),
how should the new version of the binding for target version
1.2.3 be versioned? Using 1.2.4 is not an option because it
potentially collides with the binding for the next version of the
target.
What about 1.2.3.x? How does dub handle letters in version numbers?
Maybe 1.2.3.0w would be viable ('w' for 'wrap').
--Ben
Re: Mono-D v2.4.9 - Parser fixes
On Tuesday, 23 September 2014 at 16:53:23 UTC, Andrei Alexandrescu wrote: On 9/23/14, 7:06 AM, Alexander Bothe wrote: On Tuesday, 23 September 2014 at 14:02:47 UTC, Alexander Bothe wrote: Hi everyone, just wanted to announce a further small version bump of Mono-D. And yeah, despite my 2 week-break, development still continues! Cheers, Alex Durr, forgot to put in links: Release notes: http://wiki.dlang.org/Mono-D_Release_Notes Wiki: http://wiki.dlang.org/Mono-D Github: https://github.com/aBothe/D_Parser / https://github.com/aBothe/Mono-D Awesome! I'm using it on OSX, works nice. -- Andrei Same on Linux and Windows. I think Mono-D is the last bridge before we can see a full-blown IDE written in D. I was shocked how smoothly Mono-D works compared to DDT. On linux it wasn't one click install though. I had to compile Monodevelop myself to get the plugin working. And to be fair I didn't check DDT for some time now. In short, Mono-D FTW! Alexander, thanks for your great contribution. Piotrek
