Re: DCD 0.2.0 Released
On 2013-11-14 08:36, Philippe Sigaud wrote: This project imports stdx.d.(lexer/parser/ast). Where can I find these modules? The Dscanner submodule: https://github.com/Hackerpilot/Dscanner/tree/master/stdx/d -- /Jacob Carlborg
Re: DCD 0.2.0 Released
A completion feature for emacs, I definitely need to try it ! Thanks for your work Brian. @Philippe Sigaud: On the author's other project, DScanner ( https://github.com/Hackerpilot/Dscanner). 2013/11/14 Philippe Sigaud philippe.sig...@gmail.com This project imports stdx.d.(lexer/parser/ast). Where can I find these modules? On Thu, Nov 14, 2013 at 8:19 AM, Jacob Carlborg d...@me.com wrote: On 2013-11-13 20:40, Brian Schott wrote: DCD 0.2.0 is released. Github Project: https://github.com/Hackerpilot/DCD Release Tag: https://github.com/Hackerpilot/DCD/tree/0.2.0 The D Completion Daemon is an auto-complete system for the D programming language that is not tied to any specific text editor or IDE. Modules exist for Textadept, Vim, Kate, Emacs, and Zeus. The 0.2.0 release closes 28 issues, which you can browse here: https://github.com/Hackerpilot/DCD/issues?milestone=2state=closed. The highlights of this release are improved speed, reduced memory consumption, and the ability to get the location of the declaration of a symbol at the cursor location. Notes: * Only the Textadept module has support for go-to-declaration at the moment. Pull requests to update the other modules are welcome and encouraged. * Lua's io.popen is still a pain on Windows. It causes a command window to pop up when getting completions. I'll need to figure out a way around that for 0.3.0. Awesome, keep up the good work. -- /Jacob Carlborg
Re: unit-threaded (D multithreaded unit testing library) v0.2.0 released
On Wednesday, 13 November 2013 at 13:18:39 UTC, Atila Neves wrote: http://code.dlang.org/packages/unit-threaded https://github.com/atilaneves/unit-threaded What's new? Bug fixes and the dtest util. dtest lets you point it at a list of directories, preferably just one called tests (that way there's less command-line options to type) and voilá, all tests in all subdirectories get run automagically. The way I have it set up for my projects is I have a shell script called dt that calls dtest telling it where the unit_threaded library is. All my projects now have a tests directory separate from the main source tree. When I'm at the root dir of the repo, all I have to do is type dt followed by Enter and there go the unit tests wizzing along in parallel. Edit, save, dt, repeat until the test run goes red. TDD nirvana. If I ever have my way and this takes off, I'd _really_ like to type dub test instead of dt and have it figure out dependencies itself. One can dream. So now I have my own little version of what the Go guys have with go test, whislt keeping the advantages of what the library already did. No boilerplate. Stick modules in tests in any package structure and have them all run. Nice. :) I agree that dub test would be even nicer.
Re: Introducing Build Master Andrew Edwards
Whew I almost applied for the role last night. Welcome Master Andrew. On Thu, Nov 14, 2013 at 12:45 PM, Walter Bright newshou...@digitalmars.comwrote: Please join Andrei and myself in congratulating Andrew in his new role as Build Master! Lots of people have worked on various aspects of the install packages and release builds - both Brads, Jordi, Jacob, Martin, etc. Andrew will fill the desperately needed role of getting this all organized so everyone won't have to put up with my chaotic attempts at it anymore.
Running D in the Java VM
Hey everyone! I have been experimenting for the past couple of days with an idea I had, and since I recently made a little progress I thought I would share some of what I have been doing with you. What I have done, in a nutshell, is began the process for a language converter that takes D source files, converts them into Java source files, and then compiles them as Java class files so that they can be ran on Java's VM. It is extremely limited in what it can do right now, only being able to convert/compile a simple Hello World program, but I was proud of myself for getting even that far so I wanted to brag. :P You may want to ask, Hey, man. D is a great language. Why would I ever want to convert it to Java? Normally, you wouldn't. Java blows. What I am envisioning for this project is something quite magical in my opinion. If we can take D code and have it compile into Java class files, we can then compile them into Android dex files. This would make D able to build and run on Android devices through its VM. Sure, people are working on getting D to compile to ARM binaries, but this could be another option as a Java alternative on Android.(eventually) Unfortunately I do not know much about compilers, but even in the last couple of days I feel like I have learned a great deal about what kinds of stuff goes into them. Eventually I'd like to make a full blown compiler that takes D code and can go right to dex files, but that would be something that would happen way down the road. In order to get D working on Android sooner, I figured a language converter would be the easier route. I can, and would love to go in to more detail about this, but it is getting late and this post is already quite long. Maybe I should start a blog about my D escapades? Anyways, I would love to hear feedback on this idea! Thanks for your time!
Re: Running D in the Java VM
On Fri, Nov 15, 2013 at 9:13 AM, Jeremy DeHaan dehaan.jerem...@gmail.comwrote: I can, and would love to go in to more detail about this, but it is getting late and this post is already quite long. Maybe I should start a blog about my D escapades? Anyways, I would love to hear feedback on this idea! Thanks for your time! Nice one, I have to use Java at work, it would be awesome if I didn't have to. Would be cool if you make it so that the outputs to java are just trasforms of the AST that way people could write other types of output such as C.
Re: Running D in the Java VM
On Friday, 15 November 2013 at 07:30:07 UTC, Timur Gafarov wrote: Maybe it would be better to compile D directly into JVM/Dalvik bytecode? Oh, absolutely. Like I said though, I don't really know that much about compilers so I decided to go this route. Also, it's actually been a pretty fun project so far and I see no reason to do it a different way right now.
