Re: Calypso: Direct and full interfacing to C++
http://forum.dlang.org/post/mbqt88$a6n$1...@digitalmars.com looks like C++ class support is shifting to value types.
Re: DlangIDE
On Thursday, 12 February 2015 at 14:24:05 UTC, ketmar wrote: i don't want to give you any orders, but i think that it's better to make shortcuts user-definable ASAP. you may skip GUI for that now and just make a "keymap" file of some kind, and it will still be much better than hard-coded shourtcuts. Keyboard shortcuts settings support is added. For linux and macos settings are placed in file ~/.dlangide/shortcuts.json For Windows, C:\Users\user\AppData\Roaming\.dlangide\shortcuts.json If no such file exists, it's being created on DlangIDE start, filling with default values to simplify configuration.
Re: Calypso: Direct and full interfacing to C++
Hello Elie, Ok, I tried to build on OS X with the LLVM/Clang revisions from above and the Calypso/LDC code from my github fork, but it is a no go. Calypso compiles pretty easily, but there are issues with "vector" not being found, so then I install libc++ so that clang easily picks up the correct include directories. Then "unistd.h" isn't found...ok it turns out XCode Command Line Tools needs to be installed to get some gcc specific files, but the internal Calypso call to clang needs to be modified. Change Calypso to call 'xcrun --show-sdk-path`, because this seems to work from the command line. Needs to be run from a shell...ugh. Etc, etc. Run into problems with libc++ and libstdc++ colliding. Remove libc++. Ugh. I finally just compile things by hand and get through to Calypso running and producing a bunch of object files, but then gcc won't link in some allocator code from stdc++?? Sheesh, not sure what is going on...I have tried several different ways to fix this, to no avail. Anyways, I am tired so I will just have to mess with this some more tomorrow or the next day. Hopefully I can figure out what is going on as it seems close to working. There might be real issues with someone having libc++ and libstdc++ alongside XCode tools like I had. Thanks, Kelly P.S. I try out Calypso from your github repo most days and the vector/bitset/showcase examples weren't working with todays code --> "Do not call _d_invariant on C++ class objects". Just to make sure you are aware of it.
New book: Developing with compile time in mind
Exciting news, my book on CTFE is out[0]. To summarize, it contains most of my knowledge of CTFE in a generic'ish form with examples being in D. There is a bit of talk of what support there can be and what we have. The design patterns are probably the most interesting. If you have any improvements or find any issues e.g. stray hyphens (Copied directly from Word wasn't a good idea) please let me know. The size of the book is around 51 pages. I understand if you do not consider it worth $15USD so the minimum price is $5USD. If there is demand I can create an extra package (will cost) that contains full examples on how to use the design patterns. Leanpub support sending to Kindle and will you give you a pdf, mobi and epub versions. [0] https://leanpub.com/ctfe
dbeaengine - D binding for the BeaEngine disassembler
dbeaengine[1] is a simple BeaEngine[2] interface for the D programming language. The BeaEngine is an X86 and X86_64 library which can be used to disassemble X86 and X86_64 byte-code. The programming interface is simple and outrageously easy to use (a single function named `disassemble()` ). This D binding doesn't add a layout over the original API but the `enum`, `struct` and their members names are more D-friendly. Additionaly, safety is introduced by turning `const` every data set by Bea, which avoids any unintentional modification of the results. -- The project includes: - the original C sources and some script to build the engine as an object. - the di interface, a bit tweaked as mentioned in the intro. - a Coedit project and the equivalent shell scripts to build the engine as a static library. - a sample application which disassembles itself at run-time. Misc: - mostly licensed under the terms of the LGPL v3. - credit go to the original authors, this is a simple interface! - tested under win32 and nux64. - beta, some doc. comments are missing, and `ArgType`[3] may be decomposed to avoid bit-masking. -- [1]: http://www.beaengine.org/ [2]: https://github.com/BBasile/dbeaengine [3]: https://github.com/BBasile/dbeaengine/blob/master/interface/beaengine.di#L168
Re: This Week in D - Issue 5
On Monday, 16 February 2015 at 07:14:35 UTC, Andrei Alexandrescu wrote: Oh, could you please add that DConf has a call for submissions and an early bird discount through Feb 28? it was already there - DConf 2015 is right under the stats and I keep that little section updated with the latest. (We really need your talk proposals folks. No proposals means no conference.) aye.
Re: This Week in D - Issue 5
On Monday, 16 February 2015 at 07:05:41 UTC, Meta wrote: Should be "A module"? yes, thanks!
Re: Calypso: Direct and full interfacing to C++
Hi Kelly, It's done, I've merged latest LDC upstream + your build fixes into Calypso. About Microsoft vtables they work much more differently from the Itanium ones than I thought, it's going to a lot trickier than just a few lines of code so I won't be able to make D classes inheriting from C++ ones work on MSVC until I setup a dev environment on Windows. It's just those « D-C++ classes » though, the rest has a better chance to work now.
Re: Calypso: Direct and full interfacing to C++
On Tuesday, 17 February 2015 at 01:53:22 UTC, Elie Morisse wrote: Hi Kelly, It's done, I've merged latest LDC upstream + your build fixes into Calypso. Alright, cool. I pulled it here and things build fine on Linux. Showcase and string examples work nicely. About Microsoft vtables they work much more differently from the Itanium ones than I thought, it's going to a lot trickier than just a few lines of code so I won't be able to make D classes inheriting from C++ ones work on MSVC until I setup a dev environment on Windows. Ok, developing on Win is not the nicest right now. I use Qt and it seems like the best option (change to msvc when needed...like to change the Debug/Release build types because the command line and Qt don't seem persistent). It's just those « D-C++ classes » though, the rest has a better chance to work now. Ok, I might try to build again here and see how it goes. Thanks, Kelly P.S. I HATE THIS FORUM EDITORplease add a preview button, whoever takes care of this!?!? I take notes in a different editor and then paste here and it looks fine, only to end up mangled when actually submitted...ugh :)
Re: Calypso: Direct and full interfacing to C++
On Tue, Feb 17, 2015 at 02:16:57 +, Kelly via Digitalmars-d-announce wrote: > P.S. I HATE THIS FORUM EDITORplease add a preview button, > whoever takes care of this!?!? I take notes in a different editor > and then paste here and it looks fine, only to end up mangled > when actually submitted...ugh :) You can subscribe via email. --Ben
Re: New book: Developing with compile time in mind
On 2/16/2015 3:07 PM, Rikki Cattermole wrote: [0] https://leanpub.com/ctfe Thank you. I bought my copy!
Re: New book: Developing with compile time in mind
On 17/02/2015 4:32 p.m., Walter Bright wrote: On 2/16/2015 3:07 PM, Rikki Cattermole wrote: [0] https://leanpub.com/ctfe Thank you. I bought my copy! No problem! Just let me know any improvements that could be made. Updates are free after all! (Leanpub is amazing, what with markdown writing and all).
Re: Calypso: Direct and full interfacing to C++
On Tuesday, 17 February 2015 at 02:16:58 UTC, Kelly wrote: P.S. I HATE THIS FORUM EDITORplease add a preview button, whoever takes care of this!?!? I take notes in a different editor and then paste here and it looks fine, only to end up mangled when actually submitted...ugh :) You mean wrapping? Don't wrap the text manually, server does on its own.
