Re: Beta D 2.068.0-b2
On Friday, 31 July 2015 at 17:56:23 UTC, Kelet wrote: On Friday, 31 July 2015 at 15:58:24 UTC, Gerald Jansen wrote: [...] Hi Gerald, MonoTime is the replacement for TickDuration and it's initialized from the runtime initialization function (rt_init). This is because the GC and others may need time functionality. [...] To expand on this, while MonoTime was in 2.067.1, it was not initialized in rt_init at the time. Regards, Kelet
Re: Beta D 2.068.0-b2
On Friday, 31 July 2015 at 15:58:24 UTC, Gerald Jansen wrote: I'm not sure if this is the right place to report issues. I downloaded dmd.2.068.0-b2.linux.zip, unzipped it and added the bin64 directory to my path. The standard hello.d compiles fine but segfaults immediately. Details follow. Also rdmd segfaults with the same message. (The same process with the 2.067.1 zip works fine on the same box.) Details: gjansen@gamma:~$ uname -a Linux gamma 2.6.32-279.14.1.el6.x86_64 #1 SMP Mon Oct 15 13:44:51 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux gjansen@gamma:~$ dmd --version DMD64 D Compiler v2.068.0-b2 Copyright (c) 1999-2015 by Digital Mars written by Walter Bright gjansen@gamma:~$ dmd hello.d gjansen@gamma:~$ ./hello Segmentation fault (core dumped) gjansen@gamma:~$ gdb hello snip (gdb) run Starting program: /ricerca/gjansen/hello [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x004418e1 in _d_initMonoTime () Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6_3.6.x86_64 Hi Gerald, MonoTime is the replacement for TickDuration and it's initialized from the runtime initialization function (rt_init). This is because the GC and others may need time functionality. Unfortunately, it looks like MonoTime does not currently support your kernel version. It needs at least Linux 2.6.39. The reason being is that it has the CLOCK_BOOTTIME clock which was implemented in Linux 2.6.39. Without this clock, the minimum version would be Linux 2.6.32. If I had to hazard a guess, I'd say the offending segfault is coming from calling clock_getres(clockArg, ts) (where clockArg is essentially CLOCK_BOOTTIME) in _d_initMonoTime(). It seems to call this for all supported Clocks for your platform. Hopefully some code can be added to only allow CLOCK_BOOTTIME on kernels that support it. 2.6.32 is still supported as a longterm kernel release. Regards, Kelet
Re: Dgame 0.6 - Beta
On Tuesday, 9 June 2015 at 16:30:20 UTC, Namespace wrote: I'm glad to announce the Beta of Dgame 0.6.0: https://github.com/Dgame/Dgame/releases There are some major changes, like Masks for Surfaces, the AntiAlias and OpenGl Versions enum in GLContextSettings (previous GLSettings) and so on. But for the most frequent stuff it should be backward compatible. Also new is a nice alterantive for TileMaps: VertexArrays. The relevant tutorial is currently missing, but I hope I can finish it until tomorrow. I've also made a change log (for the first time) so that each change with the corresponding commit can be tracked: http://dgame-dev.de/index.php?controller=developmentmode=changelog As always, there is also a new web page (this time probably for the last time :D): http://dgame-dev.de/ Thank you, D needs more frameworks libraries like Dgame.
Re: Coedit - beta 1 released
On Tuesday, 7 April 2015 at 05:45:16 UTC, Baz wrote: I'm pleased to announce the first beta of Coedit, the small IDE for the D programming language, based on DMD. This version introduces: - the option editor. - metad, a meta GIT repository composed of static libraries easily buildable with Coedit. - DCD integration: call tips and DDoc comments as hints. - symbol list based on libdparse (formerly called the _static explorer_) Links: - Change log and short intro to the new features: https://github.com/BBasile/Coedit/releases/tag/beta_1 - Binaries for win32: https://github.com/BBasile/Coedit/releases/download/beta_1/coedit.beta1.win32.zip - Binaries for Nux64: https://github.com/BBasile/Coedit/releases/download/beta_1/coedit.beta1.linux64.zip Hi Baz, I'm glad to see another IDE on the playing field. Interesting that it's written in FreePascal and utilizing Lazarus components. I always thought it was a good but underutilized tool set. For now, I'm just reading the wiki (which is well-populated), but I look forward to giving it a try sometime soon. Cheers!
Re: Coedit - beta 1 released
On Wednesday, 8 April 2015 at 17:58:18 UTC, Kelet wrote: On Tuesday, 7 April 2015 at 05:45:16 UTC, Baz wrote: I'm pleased to announce the first beta of Coedit, the small IDE for the D programming language, based on DMD. This version introduces: - the option editor. - metad, a meta GIT repository composed of static libraries easily buildable with Coedit. - DCD integration: call tips and DDoc comments as hints. - symbol list based on libdparse (formerly called the _static explorer_) Links: - Change log and short intro to the new features: https://github.com/BBasile/Coedit/releases/tag/beta_1 - Binaries for win32: https://github.com/BBasile/Coedit/releases/download/beta_1/coedit.beta1.win32.zip - Binaries for Nux64: https://github.com/BBasile/Coedit/releases/download/beta_1/coedit.beta1.linux64.zip Hi Baz, I'm glad to see another IDE on the playing field. Interesting that it's written in FreePascal and utilizing Lazarus components. I always thought it was a good but underutilized tool set. For now, I'm just reading the wiki (which is well-populated), but I look forward to giving it a try sometime soon. Cheers! Hi Baz, After a quick trial run, I'm quite impressed on how well it runs on my rather sluggish computer. All of the features seem to be in place and the documentation is well written. My only complaint lies in the seemingly low level of integration between coedit and DUB. DUB is quickly becoming ubiquitous in the D community. While it seems like I can build and execute my project using DUB, I have to maintain 2 separate project configurations -- one for DUB and one for coedit. Do you think you will ever be so inclined to have coedit support opening a DUB package file (i.e., dub.json)? I think that would sway me to becoming a regular user. But perhaps I misunderstand something here.. Thanks,
