Re: autowrap v0.0.1 - Automatically wrap existing D code for use in Python and Excel
On Wednesday, 18 April 2018 at 15:28:07 UTC, Atila Neves wrote: http://code.dlang.org/packages/autowrap This came out of the need at work to take existing D code and make it available for both Excel and Python. [...] Awesome. I'm also working on numpy.ndarray <-> mir.ndslice automatic wrapper https://github.com/ShigekiKarita/mir-pybuffer
Re: PixelPerfectEngine v0.9.4-alpha.2
On Monday, 16 April 2018 at 15:08:38 UTC, Chris Katko wrote: Definitely add screen shots to the github. Screenshots = Downloads. I know, currently I'm struggling with getting assets for this purpose, also with getting rid of the GC from the rendering pipeline.
Re: dxml 0.3.0 released
On Friday, April 20, 2018 16:07:06 Jesse Phillips via Digitalmars-d-announce wrote: > On Friday, 20 April 2018 at 00:46:38 UTC, Jonathan M Davis wrote: > > Yes. I would have thought that that was clear. It throws if any > > of the characters or sequence of characters in the argument > > aren't legal in the text portion of an XML document. Those > > characters that can be legally present in encoded form but not > > in their literal form can be encoded first with encodeText. > > I'll try to make the documentation clearer. > > I think I just feel it is a little hidden under the exception > list. A note in the general description about utilizing > encodeText on text which needs encoding would be good. Well, for better or worse, it now mentions it directly in the Throws section. - Jonathan M Davis
Re: GDB + ddemangle
20.04.2018 20:55, Iain Buclaw пишет: Using a compiler that implements 2.077 or later (IIRC) probably won't, due to gdb being too old. They broke ABI by introducing back referencing, no release of gdb supports that yet. I see. Thanks for clarification. Aren't plugins for gdb like subj more simple way to extend dlang support in gdb then?
Re: GDB + ddemangle
On 20 April 2018 at 17:40, drug via Digitalmars-d-announcewrote: > 20.04.2018 16:49, Iain Buclaw пишет: >> >> >> GDB auto-detects the language based on DW_LANG tag in the debug info. >> >> If you are starting up gdb without a program to debug, you can >> explicitly switch with: set lang d >> Then try something like: demangle _D3fooFiZv >> >> Or if you want it to start up in D mode: gdb -ex 'set lang d' >> > it works, thank you. But not in all cases. For example when gdb stops on > breakpoint it demangle, but if I do `bt` - backtrace isn't demangled. Using a compiler that implements 2.077 or later (IIRC) probably won't, due to gdb being too old. They broke ABI by introducing back referencing, no release of gdb supports that yet.
Re: dxml 0.3.0 released
On Friday, 20 April 2018 at 00:46:38 UTC, Jonathan M Davis wrote: Yes. I would have thought that that was clear. It throws if any of the characters or sequence of characters in the argument aren't legal in the text portion of an XML document. Those characters that can be legally present in encoded form but not in their literal form can be encoded first with encodeText. I'll try to make the documentation clearer. - Jonathan M Davis I think I just feel it is a little hidden under the exception list. A note in the general description about utilizing encodeText on text which needs encoding would be good.
Re: GDB + ddemangle
20.04.2018 16:49, Iain Buclaw пишет: GDB auto-detects the language based on DW_LANG tag in the debug info. If you are starting up gdb without a program to debug, you can explicitly switch with: set lang d Then try something like: demangle _D3fooFiZv Or if you want it to start up in D mode: gdb -ex 'set lang d' it works, thank you. But not in all cases. For example when gdb stops on breakpoint it demangle, but if I do `bt` - backtrace isn't demangled.
Re: GDB + ddemangle
On 20 April 2018 at 14:54, drug via Digitalmars-d-announcewrote: > 20.04.2018 15:36, Mike Franklin пишет: > >> On Friday, 20 April 2018 at 10:36:25 UTC, drug wrote: >>> >>> 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? >>> But how to enable it? It doesn't work out of box at least for me. >> >> >> I believe you enable it with `-demangle=dlang` >> >> The original announcement is here: >> https://forum.dlang.org/post/rvoqllpimfskvlabp...@forum.dlang.org >> >> There are a few posts on the forum with some example usages: >> https://forum.dlang.org/search?q=%22demangle%3Ddlang%22=1 >> >> Mike > > thanks for reply! but gdb don't recognize this option - unknown option > "--demangle=dlang" > > ``` > $gdb --version > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git > Copyright (C) 2016 Free Software Foundation, Inc. > ... > ``` > > Or it is intended to work only using `objdump` etc? GDB auto-detects the language based on DW_LANG tag in the debug info. If you are starting up gdb without a program to debug, you can explicitly switch with: set lang d Then try something like: demangle _D3fooFiZv Or if you want it to start up in D mode: gdb -ex 'set lang d'
Re: GDB + ddemangle
20.04.2018 15:36, Mike Franklin пишет: On Friday, 20 April 2018 at 10:36:25 UTC, drug wrote: 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me. I believe you enable it with `-demangle=dlang` The original announcement is here: https://forum.dlang.org/post/rvoqllpimfskvlabp...@forum.dlang.org There are a few posts on the forum with some example usages: https://forum.dlang.org/search?q=%22demangle%3Ddlang%22=1 Mike thanks for reply! but gdb don't recognize this option - unknown option "--demangle=dlang" ``` $gdb --version GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. ... ``` Or it is intended to work only using `objdump` etc?
Re: GDB + ddemangle
On Friday, 20 April 2018 at 12:28:03 UTC, Basile B. wrote: On Friday, 20 April 2018 at 11:06:47 UTC, Mike Wey wrote: On 20-04-18 12:36, drug wrote: 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me. It should be automatic when the executable is build with debugging info. `-g` it is not, clearly ;) The problem is that one also needs to process the compiler output in an IDE, so finally it doesn't change anything to anything
Re: GDB + ddemangle
On Friday, 20 April 2018 at 10:36:25 UTC, drug wrote: 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me. I believe you enable it with `-demangle=dlang` The original announcement is here: https://forum.dlang.org/post/rvoqllpimfskvlabp...@forum.dlang.org There are a few posts on the forum with some example usages: https://forum.dlang.org/search?q=%22demangle%3Ddlang%22=1 Mike
Re: GDB + ddemangle
On Friday, 20 April 2018 at 11:06:47 UTC, Mike Wey wrote: On 20-04-18 12:36, drug wrote: 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me. It should be automatic when the executable is build with debugging info. `-g` it is not, clearly ;)
Re: GDB + ddemangle
20.04.2018 14:06, Mike Wey пишет: On 20-04-18 12:36, drug wrote: 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me. It should be automatic when the executable is build with debugging info. `-g` is there a way to check feature availability? What version gdb should have etc?
Re: GDB + ddemangle
On 20-04-18 12:36, drug wrote: 20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me. It should be automatic when the executable is build with debugging info. `-g` -- Mike Wey
Re: GDB + ddemangle
20.04.2018 13:03, Joakim пишет: You are aware that gdb has built-in support for demangling D for 3-4 years now? But how to enable it? It doesn't work out of box at least for me.
Re: GDB + ddemangle
On Friday, 20 April 2018 at 10:03:53 UTC, Joakim wrote: On Thursday, 19 April 2018 at 12:43:36 UTC, ANtlord wrote: Hello! I've written a piece of glue code that helps to debug D code using GDB. The code glues together GDB and ddmangle. Checkout the link https://github.com/ANtlord/gdb-ddemangle PRs are welcome! You are aware that gdb has built-in support for demangling D for 3-4 years now? I've been told this too, not so long ago, but actually i still feed GDB output with ddemangle too (for Coedit 'GDB commander' widget).
Re: GDB + ddemangle
On Thursday, 19 April 2018 at 12:43:36 UTC, ANtlord wrote: Hello! I've written a piece of glue code that helps to debug D code using GDB. The code glues together GDB and ddmangle. Checkout the link https://github.com/ANtlord/gdb-ddemangle PRs are welcome! You are aware that gdb has built-in support for demangling D for 3-4 years now? http://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git=search=HEAD=commit=ibuclaw I don't know if Iain got all his patches in, but it demangles a lot of symbols for me already. However, I just started using the new lldb package in Termux, and I do miss it there. Otherwise, lldb is very nice and much more stable for me on 64-bit ARM.
Re: dxml 0.3.0 released
On Friday, 20 April 2018 at 08:45:45 UTC, Dejan Lekic wrote: Jonathan, are the interfaces in the dom module generated from the IDL code from W3C? It's not W3C DOM :)
Re: dxml 0.3.0 released
On Friday, April 20, 2018 08:45:45 Dejan Lekic via Digitalmars-d-announce wrote: > On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis > > wrote: > > Well, since I'm going to be talking about dxml at dconf, and > > it's likely that I'll be talking about stuff that was not in > > the 0.2.* releases, it seemed like I should get a new release > > out before dconf. So, here it is. > > > > dxml 0.3.0 has now been released. > > > > I won't repeat everything that's in the changelog, but the > > biggest changes are that writer support has now been added, and > > it's now possible to configure how the parser handles > > non-standard entity references. > > > > Please report any bugs that you find via github. > > > > Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html > > Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/ > > Github: https://github.com/jmdavis/dxml/tree/v0.3.0 > > Dub: http://code.dlang.org/packages/dxml > > > > - Jonathan M Davis > > I am happy to see dxml moving on! > Jonathan, are the interfaces in the dom module generated from the > IDL code from W3C? No, that's not something that I'm familiar with. I just made up the API based on what made sense to me. I basically took the API that EntityRange.Entity has and morphed it into what made sense for a tree structure. - Jonathan M Davis
Re: dxml 0.3.0 released
On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis wrote: Well, since I'm going to be talking about dxml at dconf, and it's likely that I'll be talking about stuff that was not in the 0.2.* releases, it seemed like I should get a new release out before dconf. So, here it is. dxml 0.3.0 has now been released. I won't repeat everything that's in the changelog, but the biggest changes are that writer support has now been added, and it's now possible to configure how the parser handles non-standard entity references. Please report any bugs that you find via github. Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/ Github: https://github.com/jmdavis/dxml/tree/v0.3.0 Dub: http://code.dlang.org/packages/dxml - Jonathan M Davis I am happy to see dxml moving on! Jonathan, are the interfaces in the dom module generated from the IDL code from W3C?