Re: This Week in D: Issue #4
On Thursday, 12 February 2015 at 10:06:43 UTC, Dominikus Dittes Scherkl wrote: On Wednesday, 11 February 2015 at 14:32:46 UTC, Adam D. Ruppe wrote: On Wednesday, 11 February 2015 at 11:21:46 UTC, Dominikus Dittes Scherkl wrote: Did I missed issue #5 ? No, I did; I was sick most of last week and decided to skip it, just going to bed instead on sunday night. Sorry, I didn't wanted to create any pressure. Of course health is more important. Gute Besserung! Always nice to see other german people here. :) Moin.
Re: This Week in D: Issue #4
On Wednesday, 11 February 2015 at 14:32:46 UTC, Adam D. Ruppe wrote: On Wednesday, 11 February 2015 at 11:21:46 UTC, Dominikus Dittes Scherkl wrote: Did I missed issue #5 ? No, I did; I was sick most of last week and decided to skip it, just going to bed instead on sunday night. Sorry, I didn't wanted to create any pressure. Of course health is more important. Gute Besserung!
Re: This Week in D: Issue #4
On Wednesday, 11 February 2015 at 14:32:46 UTC, Adam D. Ruppe wrote: On Wednesday, 11 February 2015 at 11:21:46 UTC, Dominikus Dittes Scherkl wrote: Did I missed issue #5 ? No, I did; I was sick most of last week and decided to skip it, just going to bed instead on sunday night. Hope you feel better, health is more important than a blog update : )
Re: This Week in D: Issue #4
On 2/11/15 6:32 AM, Adam D. Ruppe wrote: On Wednesday, 11 February 2015 at 11:21:46 UTC, Dominikus Dittes Scherkl wrote: Did I missed issue #5 ? No, I did; I was sick most of last week and decided to skip it, just going to bed instead on sunday night. I have since learned you're doing better - great! Could you please post to this group if special circumstances cause a lapse in the newsletter. Also, if that happens it would be great if the following week's newsletter covers both weeks. Thanks! -- Andrei
Re: This Week in D: Issue #4
On Wednesday, 11 February 2015 at 11:21:46 UTC, Dominikus Dittes Scherkl wrote: Did I missed issue #5 ? No, I did; I was sick most of last week and decided to skip it, just going to bed instead on sunday night.
Re: This Week in D: Issue #4
Did I missed issue #5 ?
Re: This Week in D: Issue #4
It it a good idea to keep a weekly rhythm? Perhaps one issue every two, three or even four weeks is better at this stage of the D life. Bye, bearophile
Re: This Week in D: Issue #4
On Wed, 04 Feb 2015 14:14:24 +, Adam D. Ruppe wrote: On Wednesday, 4 February 2015 at 13:50:54 UTC, wobbles wrote: p.s. Hope the search for your dog went well. Yes, we found her after she was outside for a week. Lost about 13% of her body weight and had dehydration and hypothermia, but the vet was able to treat it and it looks like she'll make a full recovery over the next month as she puts the weight back on. it's great that she's at home now. signature.asc Description: PGP signature
Re: This Week in D: Issue #4
On 4 February 2015 at 14:14, Adam D. Ruppe via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On Wednesday, 4 February 2015 at 13:50:54 UTC, wobbles wrote: p.s. Hope the search for your dog went well. Yes, we found her after she was outside for a week. Lost about 13% of her body weight and had dehydration and hypothermia, but the vet was able to treat it and it looks like she'll make a full recovery over the next month as she puts the weight back on. This is the best news I've heard all week. Iain.
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! http://arsdnet.net/this-week-in-d/feb-01.html Early bird registration open for DConf, 2015 Vision released, GUI and Windows development on the forums. Today's tip is about class destructors, and Project Spotlight makes a return to introduce simpledisplay.d, in the first in what will become a series that walks us through making a bit of a little game in D. (Expect this to not be each week, it takes me a long time to write the project spotlight and I've been very busy lately and expect to continue being busy in the coming weeks. I'll probably try to do it every other week rather than every week.) http://www.reddit.com/r/programming/comments/2uhgzr/this_week_in_d_2015_vision_released_tip_on/ https://twitter.com/adamdruppe/status/562112301248290816 Thanks adam. The simpledisplay.d stuff is very interesting. Must play around with it soon! p.s. Hope the search for your dog went well.
Re: This Week in D: Issue #4
On Wednesday, 4 February 2015 at 13:50:54 UTC, wobbles wrote: p.s. Hope the search for your dog went well. Yes, we found her after she was outside for a week. Lost about 13% of her body weight and had dehydration and hypothermia, but the vet was able to treat it and it looks like she'll make a full recovery over the next month as she puts the weight back on.
Re: This Week in D: Issue #4
On Wednesday, 4 February 2015 at 14:14:27 UTC, Adam D. Ruppe wrote: On Wednesday, 4 February 2015 at 13:50:54 UTC, wobbles wrote: p.s. Hope the search for your dog went well. Yes, we found her after she was outside for a week. Lost about 13% of her body weight and had dehydration and hypothermia, but the vet was able to treat it and it looks like she'll make a full recovery over the next month as she puts the weight back on. Great, very glad there was a happy ending!
Re: This Week in D: Issue #4
On Mon, 02 Feb 2015 04:57:09 +, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! OT: just used your `arsd.cgi` to write a simple web-service (internal service using to decode some binary files to text). it took me about ten minutes, including reading comments in cgi.d, and works like a charm. sure, it's not ready for big internets, but it solves my task perfectly. thank you. signature.asc Description: PGP signature
Re: This Week in D: Issue #4
On Wednesday, 4 February 2015 at 14:14:27 UTC, Adam D. Ruppe wrote: On Wednesday, 4 February 2015 at 13:50:54 UTC, wobbles wrote: the vet was able to treat it and it looks like she'll make a full recovery over the next month as she puts the weight back on. Wow. She is a fighter. Glad to hear that everything is OK now.
Re: This Week in D: Issue #4
On Wednesday, 4 February 2015 at 14:34:18 UTC, eles wrote: Wow. She is a fighter. Glad to hear that everything is OK now. Aye, I really don't know how she survived some of those nights, below zero temperatures (Fahrenheit - so actually cold) with nasty wind from that storm that hit the eastern US last week. But she did.
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 09:23:43 UTC, Ulrich Küttler wrote: $ dmd window.d simpledisplay.d color.d simpledisplay.d(550): Error: module color is in file Huh, that should work, did you remember to download color.d to the same directory too?
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 05:53:30 UTC, Jeremy DeHaan wrote: Yes, they are not guaranteed to run, but isn't that only during run time? They are going to be called at the application exit to ensure everything is cleaned up. If the application exits somewhat cleanly (through return from main or even a thrown exception in D), it will run, though I'm not sure if that's guaranteed or just an implementation convenience. However, if the application exits differently, they won't necessarily be run. For example, a Unix signal terminating the process skips all the D cleanup tasks. Often, this doesn't matter because the operating system will clean up a lot of resources anyway. But if you are using something like shared memory with another process, or expect a file to be written to in a destructor, you'll find those things never happen. I had this problem once in simpledisplay.d. When it died by ctrl+c, the unix SIGINT was sent, and that skipped the destructors for shared images. As a result, the system eventually ran out of shared handles and most GUI programs wouldn't start up anymore until I cleaned it up some other way.
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 14:34:13 UTC, Adam D. Ruppe wrote: On Tuesday, 3 February 2015 at 09:23:43 UTC, Ulrich Küttler wrote: $ dmd window.d simpledisplay.d color.d simpledisplay.d(550): Error: module color is in file Huh, that should work, did you remember to download color.d to the same directory too? Yes, I did. Now, I am confused about this, since it did not work yesterday (I still have the terminal output) but it does now. Here is what I did: $ cd arsd $ git pull $ dmd window.d simpledisplay.d color.d simpledisplay.d(550): Error: module color is in file $ mkdir arsd $ cp color.d arsd/ $ dmd window.d simpledisplay.d arsd/color.d # works $ rm -rf arsd $ dmd window.d simpledisplay.d color.d # works as well This is an error on my part, most definitely. However, rdmd still refuses to work $ rdmd window.d simpledisplay.d(550): Error: module color is in file 'arsd/color.d' which cannot be read
Re: This Week in D: Issue #4
On Tue, 03 Feb 2015 02:57:46 +, Adam D. Ruppe wrote: If you're not posting original content, what are you posting? hey guys i found this really great link on reddit... you got it! reddit is a bunch of freaks who are browsing internets the whole day and posting links to content. so they naturally don't like people who can actually *make* that content. signature.asc Description: PGP signature
Re: This Week in D: Issue #4
On Tue, 03 Feb 2015 05:53:26 +, Jeremy DeHaan wrote: I've never liked the phrasing about destructors. Yes, they are not guaranteed to run, but isn't that only during run time? They are going to be called at the application exit to ensure everything is cleaned up. nope, it's not guaranteed too. runtime is free to just kill itself without running any destructors. signature.asc Description: PGP signature
Re: This Week in D: Issue #4
On 2/3/2015 6:23 PM, Ulrich =?UTF-8?B?S8O8dHRsZXIi?= kuett...@gmail.com wrote: On Tuesday, 3 February 2015 at 02:29:23 UTC, Adam D. Ruppe wrote: On Monday, 2 February 2015 at 23:11:22 UTC, Ulrich Küttler wrote: Unfortunately, your project Spotlight does not work exactly as advertised, since simpledisplay imports arsd.color. Just to let you know. I mentioned that, which part specifically didn't work for you? What I got is $ dmd window.d simpledisplay.d color.d simpledisplay.d(550): Error: module color is in file 'arsd/color.d' which cannot be read import path[0] = /usr/include/dmd/phobos import path[1] = /usr/include/dmd/druntime/import This is dmd v2.066.1. But then, it might be my machine. Apologies if this is unhelpful. You might want to try: cd .. dmd -Iarsd arsd/window.d arsd/simpledisplay.d arsd/color.d
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 14:36:58 UTC, Adam D. Ruppe wrote: On Tuesday, 3 February 2015 at 05:53:30 UTC, Jeremy DeHaan wrote: Yes, they are not guaranteed to run, but isn't that only during run time? They are going to be called at the application exit to ensure everything is cleaned up. If the application exits somewhat cleanly (through return from main or even a thrown exception in D), it will run, though I'm not sure if that's guaranteed or just an implementation convenience. However, if the application exits differently, they won't necessarily be run. For example, a Unix signal terminating the process skips all the D cleanup tasks. Often, this doesn't matter because the operating system will clean up a lot of resources anyway. But if you are using something like shared memory with another process, or expect a file to be written to in a destructor, you'll find those things never happen. I had this problem once in simpledisplay.d. When it died by ctrl+c, the unix SIGINT was sent, and that skipped the destructors for shared images. As a result, the system eventually ran out of shared handles and most GUI programs wouldn't start up anymore until I cleaned it up some other way. Yikes, that's good to know. Still, I feel like it could be worded a little better in the docs and anywhere else they are talked about. I feel like it is just far too ambiguous.
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 02:29:23 UTC, Adam D. Ruppe wrote: On Monday, 2 February 2015 at 23:11:22 UTC, Ulrich Küttler wrote: Unfortunately, your project Spotlight does not work exactly as advertised, since simpledisplay imports arsd.color. Just to let you know. I mentioned that, which part specifically didn't work for you? What I got is $ dmd window.d simpledisplay.d color.d simpledisplay.d(550): Error: module color is in file 'arsd/color.d' which cannot be read import path[0] = /usr/include/dmd/phobos import path[1] = /usr/include/dmd/druntime/import This is dmd v2.066.1. But then, it might be my machine. Apologies if this is unhelpful.
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 05:53:30 UTC, Jeremy DeHaan wrote: On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: I've never liked the phrasing about destructors. Yes, they are not guaranteed to run, but isn't that only during run time? They are going to be called at the application exit to ensure everything is cleaned up. I would rather go with the term finalizers for those in D. A maybe useful link that quite clearly defines some concepts: http://sanjaysainitech.blogspot.com/2007/06/difference-between-destructor-dispose.html
Re: This Week in D: Issue #4
On Tuesday, 3 February 2015 at 09:08:07 UTC, eles wrote: On Tuesday, 3 February 2015 at 05:53:30 UTC, Jeremy DeHaan wrote: On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: A maybe useful link that quite clearly defines some concepts: http://sanjaysainitech.blogspot.com/2007/06/difference-between-destructor-dispose.html And this: http://stackoverflow.com/a/8299222/1284631
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! http://arsdnet.net/this-week-in-d/feb-01.html Early bird registration open for DConf, 2015 Vision released, GUI and Windows development on the forums. Today's tip is about class destructors, and Project Spotlight makes a return to introduce simpledisplay.d, in the first in what will become a series that walks us through making a bit of a little game in D. (Expect this to not be each week, it takes me a long time to write the project spotlight and I've been very busy lately and expect to continue being busy in the coming weeks. I'll probably try to do it every other week rather than every week.) http://www.reddit.com/r/programming/comments/2uhgzr/this_week_in_d_2015_vision_released_tip_on/ https://twitter.com/adamdruppe/status/562112301248290816 I'm not sure if every week needs a post to reddit. You're likely to increase the number of people who feel it is spam: https://www.reddit.com/r/programming/comments/2uhgzr/this_week_in_d_2015_vision_released_tip_on/co8v9y5 Besides, there may be weeks we want to obtain more attraction and that can be hard to do if every week is always posted. Remember, those who have found this week interested are either following it with RSS, this forum, or /r/d_language
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! Very nice! Thank you. Unfortunately, your project Spotlight does not work exactly as advertised, since simpledisplay imports arsd.color. Just to let you know.
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! http://arsdnet.net/this-week-in-d/feb-01.html Early bird registration open for DConf, 2015 Vision released, GUI and Windows development on the forums. Today's tip is about class destructors, and Project Spotlight makes a return to introduce simpledisplay.d, in the first in what will become a series that walks us through making a bit of a little game in D. (Expect this to not be each week, it takes me a long time to write the project spotlight and I've been very busy lately and expect to continue being busy in the coming weeks. I'll probably try to do it every other week rather than every week.) http://www.reddit.com/r/programming/comments/2uhgzr/this_week_in_d_2015_vision_released_tip_on/ https://twitter.com/adamdruppe/status/562112301248290816 Very nice, once again. Looking forward to next part of simpledisplay tutorial. Goal should be to make it run on iOS in 2015 ;)
Re: This Week in D: Issue #4
On 2015-02-02 at 05:57, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! http://arsdnet.net/this-week-in-d/feb-01.html It's great! I have to wonder though, why have you chosen this naming convention: jan-12, jan-18, jan-25, feb-01, ... instead of just 1, 2, ... ? That would make navigation between issues much easier, even without the page with a list of all issues (which I am unable to find). :)
Re: This Week in D: Issue #4
Another bit that confuses me: While it's not an official and hard rule, it is still against reddiquette to post your own content repeatedly and exclusively. If you're not posting original content, what are you posting? hey guys i found this really great link on reddit... idk, maybe I don't get out enough on the Internet.
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 19:52:02 UTC, Jesse Phillips wrote: I'm not sure if every week needs a post to reddit. You're likely to increase the number of people who feel it is spam: Maybe, I kinda think it might be a bit much sometimes too, but on the other hand, it is just once a week. Besides, there may be weeks we want to obtain more attraction and that can be hard to do if every week is always posted. that's a good point Remember, those who have found this week interested are either following it with RSS, this forum, or /r/d_language This #4 I think will get the word out to most people so maybe I'll let off it on reddit next week, we'll see.
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 23:11:22 UTC, Ulrich Küttler wrote: Unfortunately, your project Spotlight does not work exactly as advertised, since simpledisplay imports arsd.color. Just to let you know. I mentioned that, which part specifically didn't work for you?
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 04:57:10 UTC, Adam D. Ruppe wrote: I can't believe it, but yet another week has already passed, so up late to release this again! http://arsdnet.net/this-week-in-d/feb-01.html Early bird registration open for DConf, 2015 Vision released, GUI and Windows development on the forums. Today's tip is about class destructors, and Project Spotlight makes a return to introduce simpledisplay.d, in the first in what will become a series that walks us through making a bit of a little game in D. (Expect this to not be each week, it takes me a long time to write the project spotlight and I've been very busy lately and expect to continue being busy in the coming weeks. I'll probably try to do it every other week rather than every week.) http://www.reddit.com/r/programming/comments/2uhgzr/this_week_in_d_2015_vision_released_tip_on/ https://twitter.com/adamdruppe/status/562112301248290816 I've never liked the phrasing about destructors. Yes, they are not guaranteed to run, but isn't that only during run time? They are going to be called at the application exit to ensure everything is cleaned up.
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 13:27:33 UTC, FG wrote: That would make navigation between issues much easier, even without the page with a list of all issues (which I am unable to find). :) The naming convention was probably a mistake, if nothing else, it'll get confusing next year. But you can get a list of all of them with the rss link http://arsdnet.net/this-week-in-d/twid.rss
Re: This Week in D: Issue #4
On Monday, 2 February 2015 at 12:39:18 UTC, Szymon Gatner wrote: Looking forward to next part of simpledisplay tutorial. Goal should be to make it run on iOS in 2015 ;) I don't use any Apple hardware, so someone else would have to own that part of the code...
This Week in D: Issue #4
I can't believe it, but yet another week has already passed, so up late to release this again! http://arsdnet.net/this-week-in-d/feb-01.html Early bird registration open for DConf, 2015 Vision released, GUI and Windows development on the forums. Today's tip is about class destructors, and Project Spotlight makes a return to introduce simpledisplay.d, in the first in what will become a series that walks us through making a bit of a little game in D. (Expect this to not be each week, it takes me a long time to write the project spotlight and I've been very busy lately and expect to continue being busy in the coming weeks. I'll probably try to do it every other week rather than every week.) http://www.reddit.com/r/programming/comments/2uhgzr/this_week_in_d_2015_vision_released_tip_on/ https://twitter.com/adamdruppe/status/562112301248290816
