Re: This Week in D, issue 1
On 1/14/15 1:07 PM, Dicebot wrote: On Wednesday, 14 January 2015 at 20:20:30 UTC, Adam D. Ruppe wrote: On Wednesday, 14 January 2015 at 20:18:55 UTC, Andrei Alexandrescu wrote: Wait, no subrepo under dlang.org? -- Andrei My thought was in-progress goes under something i can push to at any time, then I'd to a PR for the finished project. But it can move to dlang.org too, however you want it to work. Just give Adam full push access to dlang.org repo ;) Done. Adam, proceed whichever way is easier until we work the kinks out. -- Andrei
Re: This Week in D, issue 1
On 1/14/15 8:21 AM, Adam D. Ruppe wrote: GitHub repo started: https://github.com/adamdruppe/This-Week-in-D Wait, no subrepo under dlang.org? -- Andrei
Re: This Week in D, issue 1
On Wednesday, 14 January 2015 at 20:20:30 UTC, Adam D. Ruppe wrote: On Wednesday, 14 January 2015 at 20:18:55 UTC, Andrei Alexandrescu wrote: Wait, no subrepo under dlang.org? -- Andrei My thought was in-progress goes under something i can push to at any time, then I'd to a PR for the finished project. But it can move to dlang.org too, however you want it to work. Just give Adam full push access to dlang.org repo ;)
DConf 2015 discounted hotel rooms now available
https://twitter.com/D_Programming/status/555471499893944323 They're available through May 12, but the number of rooms reserved is reserved and first-come-first-served, so book soon. Many thanks to Chuck Allison for facilitating this! Andrei
Re: This Week in D, issue 1
On Wednesday, 14 January 2015 at 20:18:55 UTC, Andrei Alexandrescu wrote: Wait, no subrepo under dlang.org? -- Andrei My thought was in-progress goes under something i can push to at any time, then I'd to a PR for the finished project. But it can move to dlang.org too, however you want it to work.
Re: Anyone interested in embedding a JVM in their D app?
On 15/01/2015 3:26 a.m., Ben Boeckel via Digitalmars-d-announce wrote: On Wed, Jan 14, 2015 at 15:05:18 +1300, Rikki Cattermole via Digitalmars-d-announce wrote: Definitely need to get JNI support first class. It definitely will help with getting D on Android. My experience is that the D runtime needed some work to accept that there are Linux machines without glibc (bionic for Android). After getting those assumptions out, I had it to a point where it was compiling, but things blew up in the runtime somewhere (or bionic; it was never really giving useful backtraces) during my argument parsing (my guess is the GC was mucking with the wrong bits, but there wasn't anything conclusive since debugging was never easier than what I got from logcat and looking at disassemblies). This was back in 2.065 era though and I haven't done much with it since then. --Ben That's trying to get JNI to work, I'm assuming that part has already been done and we want a nice wrapper around it. At the worse case scenario, at least it'll work for e.g. Windows, OSX and Linux.
Re: This Week in D, issue 1
On Wed, Jan 14, 2015 at 23:02:47 +, Adam D. Ruppe via Digitalmars-d-announce wrote: On Wednesday, 14 January 2015 at 22:19:12 UTC, qznc wrote: Next medium: E-Mail newsletter. Aye, it is on my list (and actually trivial, I probably have just done it in the amount of time I've spent saying it's on the list lol) And for those who like NNTP over email: http://gwene.org/ --Ben
Re: This Week in D, issue 1
On Wednesday, 14 January 2015 at 14:43:51 UTC, Adam D. Ruppe wrote: Once the bugs are worked out, like half of this can be automated too and the other half can be written some time in advance. For example, I now have the next two tip of the week bits written already (and if something else comes up, I'll just put them to the backlog, there's no time sensitivity or order requirements for these tips, they stand alone). I don't want it to be too automated, I think that's not very interesting, but I am doing some of it that way to keep it more consistent. Worst case, if I'm too busy in a week to do something new, I can just slap together the automatic list of links, paste in a tip from the backlog, and call it good enough for now, You have to synch it with your natural energy. Some weeks, just a few little tips. A lot of pots brewing in the background, but none come to the fore that week. Then periodically, a big soup. Solicit articles when a big issue is coming up - it will probably spur people into writing more. Curating content has become a somewhat thankless job since the death of print, but people still love rituals. For example, an annual conference is just as important as a ritual as it is a place to learn. It's fantastic that you've started this, BTW!
Re: This Week in D, issue 1
Yeah, I'm already thinking of a special edition around the dconf time where it'll probably be much longer than the regular editions where we'll see about writing up summaries of the talks. Then as the videos hit youtube, we'll revisit the subject in more depth in writing. (by we i hope it means like everyone, but even if it is just me, it should be OK. I plan on attending the whole conference in person this year and if I can plug in my laptop i should be able to keep up with some stuff in real time)
Re: This Week in D, issue 1
On Tuesday, 13 January 2015 at 17:30:53 UTC, Adam D. Ruppe wrote: First draft of the rss feed: http://arsdnet.net/this-week-in-d/twid.rss Subscribed. Next medium: E-Mail newsletter. There are lots of people who prefer mail over RSS. Additionally, you get to collect mail addresses, which is valuable in itself.
Re: DConf 2015 Call for Submissions is now open
On Wednesday, 14 January 2015 at 14:13:04 UTC, Daniel Murphy wrote: Brad Anderson wrote in message news:jcidebafygjtdsabn...@forum.dlang.org... Sounds like a good subject for Daniel Murphy to talk about. He spent a good hour explaining to me how a linker works in the Aloft bar after most people had retired (thanks for that, Daniel) and he certainly knows dmd extremely well. I am considering proposing a talk about ddmd, which would touch on some of the compiler internals. We'll see. This. Please do this.
Re: Anyone interested in embedding a JVM in their D app?
I think the goal of this may be backwards of what most people are thinking. What I am trying for is not to write extensions to a java app in D through JNI. Anyone is welcome to use any of this work to achieve that if they'd like. The actual goal is to embed a JVM inside of a D program. This is actually a practice from C++ that happens more than one would think. This also makes several things easier as the D subsystem is correctly initialized. There are several things that come with Java APIs only. A few that come to mind are some database drivers (hsql recommends doing JNI from C++ to Java to use their driver). Anyone familiar with hadoop, their remote file system driver is the same way (in older versions anyways). They do provide a c library that does the embedding for you (so you may not of noticed). There are other languages that do this to take advantage of the massive amount of DB support in java (last time I checked that's how DB drivers in R worked). Anyone familiar with doing this from C or C++ knows it looks nothing like java though. If you look at https://github.com/jamesmahler/djvm#example ... that's the equivalent of System.out.println(100) with the cleaned up api in djvm. While using JNI inside a java app is messy... using JNI inside a C app is sometimes way easier. Anyways, you are free to continue discussing trying to use D in Android. I'd be willing to share any information and try to assist with that project as able. On Wednesday, 14 January 2015 at 09:29:25 UTC, Russel Winder via Digitalmars-d-announce wrote: On Wed, 2015-01-14 at 02:00 +, james via Digitalmars-d-announce wrote: I've been playing with jni.h and D. I think I've got a fully working jni.d and I have the start of a nicer D wrapper around it with djvm.d. Whilst I have tinkered with JNI, I have never had to really use it in anger. And I, and many others, really want to keep it that way even though there are many who use it. It's like trying to program Python from C, only worse performance. There is JNA of course, which does some similar stuff, many use that I have never used it. The current fashion is (or will be) JNR (which leads to JEP 191). As far as I know JNA, JNR (and JEP 191) use JNI, more or less because they have to. The issue is to make using the adaptor as easy as possible. JNI is not easy; JNA is easy but slow; JNR is supposedly easy and fast, so hopefully JEP 191 will be.
Re: This Week in D, issue 1
On Tuesday, 13 January 2015 at 14:08:58 UTC, Adam D. Ruppe wrote: I've started writing a weekly D newsletter. Here's the first issue, any feedback welcome! http://arsdnet.net/this-week-in-d/jan-12.html In the future, I intend to have it written by Saturday for a weekend release, so if you want something to appear this week, please try to get it to by before then. Very nice, thank you! One suggestion. The link to emplace source code is done by linenumber on master. It would be better to link to a tag to keep the link correct. Instead of: https://github.com/D-Programming-Language/phobos/blob/master/std/conv.d#L3907 https://github.com/D-Programming-Language/phobos/blob/v2.067.0-b1/std/conv.d#L3847
Re: D idioms list
For optimal AA lookup, this idiom is also nice if you only need the result for one line: if (auto found = key in AA) do_stuff (found);
Re: This Week in D, issue 1
Once the bugs are worked out, like half of this can be automated too and the other half can be written some time in advance. For example, I now have the next two tip of the week bits written already (and if something else comes up, I'll just put them to the backlog, there's no time sensitivity or order requirements for these tips, they stand alone). I don't want it to be too automated, I think that's not very interesting, but I am doing some of it that way to keep it more consistent. Worst case, if I'm too busy in a week to do something new, I can just slap together the automatic list of links, paste in a tip from the backlog, and call it good enough for now,
Re: DConf 2015 Call for Submissions is now open
Jonathan M Davis via Digitalmars-d-announce wrote in message news:mailman.4595.1421160931.9932.digitalmars-d-annou...@puremagic.com... On Tuesday, January 13, 2015 14:39:42 Iain Buclaw via Digitalmars-d-announce wrote: Daniel prefers to talk through other peoples talks. :o) Or to work on the compiler during their talks. ;) - Jonathan M Davis I'd deny it but there's video evidence. I'm going to blame it on too much coffee.
Re: Anyone interested in embedding a JVM in their D app?
On Wed, Jan 14, 2015 at 15:05:18 +1300, Rikki Cattermole via Digitalmars-d-announce wrote: Definitely need to get JNI support first class. It definitely will help with getting D on Android. My experience is that the D runtime needed some work to accept that there are Linux machines without glibc (bionic for Android). After getting those assumptions out, I had it to a point where it was compiling, but things blew up in the runtime somewhere (or bionic; it was never really giving useful backtraces) during my argument parsing (my guess is the GC was mucking with the wrong bits, but there wasn't anything conclusive since debugging was never easier than what I got from logcat and looking at disassemblies). This was back in 2.065 era though and I haven't done much with it since then. --Ben
Re: Binutils 2.25 Released - New D demangling support
On 2015-01-14 09:46, Iain Buclaw via Digitalmars-d-announce wrote: I can't comment on that. Maybe via Macports? Otherwise if BSD have their own linker, someone will need to go and get friendly with the developers up their toolchain. Right, forgot about that the toolchain is BSD based. -- /Jacob Carlborg
Re: This Week in D, issue 1
On Wednesday, 14 January 2015 at 13:19:58 UTC, Iain Buclaw via Digitalmars-d-announce wrote: On the other hand, it's easy to loose track of things going on. Yeah, I'll forget about things then. A monthly one might be a wrap-up made by editing the weekly ones to the biggest bits and maybe writing more original articles, but I don't want to commit to it since I have a lot to do as it is...
Re: Anyone interested in embedding a JVM in their D app?
On 2015-01-14 03:00, james wrote: I've been playing with jni.h and D. I think I've got a fully working jni.d and I have the start of a nicer D wrapper around it with djvm.d. https://github.com/jamesmahler/djvm There is an example usage in the README.md. There's also why I'd do such a thing in there. I'm not sure if anyone else would be interested in this. I'm open to help and merge requests if anyone wants to join in. In the short term, I still have several low level things to wrap with the more D interfaces. In the longer term, I want to have D interfaces around JDBC. Dropbox has a tool [1] for automatically generate the JNI glue code for connecting Java - C++. Perhaps it's possible to output D code instead. [1] https://github.com/dropbox/djinni -- /Jacob Carlborg
My LLVM talk @ FOSDEM'15
Hi everybody! Like last year I am a speaker in the LLVM toolchain devroom @ FOSDEM'15. This time it is not D related but more about LLVM internals. (For sure, it is related to my work on LDC!) Read the announcement at https://fosdem.org/2015/schedule/event/llvm_internal_asm/. FOSDEM is a two-day event organised by volunteers to promote the widespread use of open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best open source conference in Europe. Regards, Kai
Re: This Week in D, issue 1
GitHub repo started: https://github.com/adamdruppe/This-Week-in-D
Re: Binutils 2.25 Released - New D demangling support
On Wednesday, 14 January 2015 at 14:42:09 UTC, Jacob Carlborg wrote: On 2015-01-14 09:46, Iain Buclaw via Digitalmars-d-announce wrote: I can't comment on that. Maybe via Macports? Otherwise if BSD have their own linker, someone will need to go and get friendly with the developers up their toolchain. Right, forgot about that the toolchain is BSD based. I was curious what they're actually using these days, so I looked it up. Appears to be some APS-licensed Mach-O linker they wrote themselves in C++: http://opensource.apple.com/tarballs/ld64/
Re: Binutils 2.25 Released - New D demangling support
On 14 January 2015 at 07:30, Jacob Carlborg via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On 2015-01-13 22:31, Iain Buclaw wrote: Hi, I'm not sure when it was announced, but binutils 2.25 has been released! There's a small reason for excitement as it is the first to come with D demangling support in the GNU toolchain. Is this something what will work on OS X? I'm not sure how much of the GNU toolchain is still being used. I can't comment on that. Maybe via Macports? Otherwise if BSD have their own linker, someone will need to go and get friendly with the developers up their toolchain.
Re: Binutils 2.25 Released - New D demangling support
Awesome work, thanks! Already available on Arch Linux indeed, just typed objdump as per your post and it worked. Editing my dmd.conf right now. Atila On Tuesday, 13 January 2015 at 21:31:15 UTC, Iain Buclaw wrote: Hi, I'm not sure when it was announced, but binutils 2.25 has been released! There's a small reason for excitement as it is the first to come with D demangling support in the GNU toolchain. Unfortunately, I forgot to send in patches that actually document it! So for the moment, it's a little secret feature shared between all who may read this. :o) How do you use it? --- By default, binutils programs will treat all mangled symbols as C++, however you can override this by using --demangle=dlang, eg: objdump -d --demangle=dlang prog.o nm --demangle=dlang ddmd You can also kickstart your usage by putting -L--demangle=dlang in your dmd.conf, and watch your obscure linker errors turn into pretty function signatures. How do I get it? --- The release itself is a source package, however a safer choice is to get the release binaries through your Linux distributor. Fortunately, there have been distributions who have been shipping it as early as three weeks ago. Archlinux users: I'd imagine this is available to use now. Ubuntu users: You'll have to wait until April with the 15.04 release. Bugs and Fixes --- Whilst the demangler is able to handle all things core.demangle can do (and a little bit more!), a small test of running nm against the ddemangle program that gets shipped with dmd 2.066 shows that there are still plenty of complex template symbols that it still can't manage. The implementation itself is pretty straightforward to follow, well documented and written in C. Volunteers who wish to help out getting as close to 99.99% coverage as possible are welcome! Enjoy! Iain.
Re: Anyone interested in embedding a JVM in their D app?
On Wed, 2015-01-14 at 02:00 +, james via Digitalmars-d-announce wrote: I've been playing with jni.h and D. I think I've got a fully working jni.d and I have the start of a nicer D wrapper around it with djvm.d. Whilst I have tinkered with JNI, I have never had to really use it in anger. And I, and many others, really want to keep it that way even though there are many who use it. It's like trying to program Python from C, only worse performance. There is JNA of course, which does some similar stuff, many use that I have never used it. The current fashion is (or will be) JNR (which leads to JEP 191). As far as I know JNA, JNR (and JEP 191) use JNI, more or less because they have to. The issue is to make using the adaptor as easy as possible. JNI is not easy; JNA is easy but slow; JNR is supposedly easy and fast, so hopefully JEP 191 will be. -- 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: Anyone interested in embedding a JVM in their D app?
On Wednesday, 14 January 2015 at 09:29:25 UTC, Russel Winder via Digitalmars-d-announce wrote: On Wed, 2015-01-14 at 02:00 +, james via Digitalmars-d-announce wrote: I've been playing with jni.h and D. I think I've got a fully working jni.d and I have the start of a nicer D wrapper around it with djvm.d. Whilst I have tinkered with JNI, I have never had to really use it in anger. And I, and many others, really want to keep it that way even though there are many who use it. It's like trying to program Python from C, only worse performance. Performance is good enough if you do the same approach as remote method invocation, by using a single call and not multiple ones. There is JNA of course, which does some similar stuff, many use that I have never used it. The current fashion is (or will be) JNR (which leads to JEP 191). As far as I know JNA, JNR (and JEP 191) use JNI, more or less because they have to. The issue is to make using the adaptor as easy as possible. JNI is not easy; JNA is easy but slow; JNR is supposedly easy and fast, so hopefully JEP 191 will be. JNI is hard on purpose. Mark Reinhold has said during the JavaONE 2014 that it was made so, to force Java developers to stay away from writing unsafe code, specially given Java's portability goal. Now with Java being adopted left and right for HPT and big data, that is an hindrance for integrating legacy code, hence the need for JNR, born out of JRuby project. Interesting enough, something like JNR was one of Microsoft extensions to Java and the precursor of .NET P/Invoke. -- Paulo
Re: This Week in D, issue 1
On 14 January 2015 at 09:53, ponce via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On Tuesday, 13 January 2015 at 14:08:58 UTC, Adam D. Ruppe wrote: I've started writing a weekly D newsletter. Here's the first issue, any feedback welcome! http://arsdnet.net/this-week-in-d/jan-12.html In the future, I intend to have it written by Saturday for a weekend release, so if you want something to appear this week, please try to get it to by before then. Very nice! I don't have enough time to keep track of all interesting discussions or interesting language change so this is much appreciated. However, to make it sustainable I would also suggest to make it This month in D, the content would feel more curated and dense, also less work to do. On the other hand, it's easy to loose track of things going on. Maybe the middle-ground would be This month in D - updated weekly ?
Re: This Week in D, issue 1
On 1/13/15 10:17 PM, Zach the Mystic wrote: Great to know this is a collaborative effort. Suggestion, though: Every month, call it This Month in D, and summarize the big picture. Putting this out every week without summarizing larger amounts of thought and energy will probably feel too frenetic. Creativity moves in arcs of differing duration. Likewise, chunks of Months - This Season in D every three months. Noice. Adam, I'll leave this suggestion up to you. -- Andrei
Re: Heady House Hunting with D
On Wednesday, 14 January 2015 at 04:23:18 UTC, Nick Sabalausky wrote: On 01/13/2015 10:56 PM, Rikki Cattermole wrote: On 14/01/2015 4:46 p.m., Philpax wrote: Hey everyone, I recently wrote a blog post about how I used D/vibe.d to help find a new house. I haven't publicized it anywhere else yet, so I'm looking forward to what the D community has to say! You can check it out here: http://philpax.me/blog/heady-house-hunting-with-d Definitely would be interesting to see this as a full blown comparison site, like there is for flight. Yea, definitely. The listing sites from the realty companies are truly horrible (and a very solid case IMO for why the web should be plain-old-data, not dynamic/rich-content). A sane front-end for all their goofy bloated half-broken crap would be great for anyone facing the royal pain of house hunting. I have had good results in the UK with rightmove, which does exactly that (although it's still a pain). They do list US (and other) properties too, but I don't think a high percentage.
Re: DConf 2015 Call for Submissions is now open
Brad Anderson wrote in message news:jcidebafygjtdsabn...@forum.dlang.org... Sounds like a good subject for Daniel Murphy to talk about. He spent a good hour explaining to me how a linker works in the Aloft bar after most people had retired (thanks for that, Daniel) and he certainly knows dmd extremely well. I am considering proposing a talk about ddmd, which would touch on some of the compiler internals. We'll see.
