Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Tuesday, 14 January 2014 at 05:04:42 UTC, Alexander Bothe wrote: On Tuesday, 14 January 2014 at 04:15:50 UTC, evilrat wrote: "ApplicationName='gdb', CommandLine=-quiet -fullname -i=mi2', CurrentDirectory=", NativeError= Cannot find the specified file Okay, I think I'm gonna make a separate option panel then for setting up the path to gdb. ok, thanks.
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Tuesday, 14 January 2014 at 04:15:50 UTC, evilrat wrote: "ApplicationName='gdb', CommandLine=-quiet -fullname -i=mi2', CurrentDirectory=", NativeError= Cannot find the specified file Okay, I think I'm gonna make a separate option panel then for setting up the path to gdb.
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Tuesday, 14 January 2014 at 04:10:03 UTC, evilrat wrote: On Monday, 13 January 2014 at 14:50:05 UTC, Alexander Bothe wrote: So according to Jacob's comment it's actually possible to get gdb on OSX - but probably just with a wrong build configuration, i.e. the mi2 interface for gdb is not available - or is it? Just try executing gdb --interpreter=mi2 to see whether Mono-D is able to handle its output properly. running "gdb --interpreter=mi2" launches it without any warnings and errors. (my gdb version is 7.6) but running mono-d debug gives following error message "ApplicationName='gdb', CommandLine=-quiet -fullname -i=mi2', CurrentDirectory=", NativeError= Cannot find the specified file
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Monday, 13 January 2014 at 14:50:05 UTC, Alexander Bothe wrote: So according to Jacob's comment it's actually possible to get gdb on OSX - but probably just with a wrong build configuration, i.e. the mi2 interface for gdb is not available - or is it? Just try executing gdb --interpreter=mi2 to see whether Mono-D is able to handle its output properly. running "gdb --interpreter=mi2" launches it without any warnings and errors. (my gdb version is 7.6)
Re: std.signal : voting has begun
On Monday, 13 January 2014 at 17:36:22 UTC, Robert M. Münch wrote: On 2014-01-13 13:50:09 +, Dicebot said: To everyone: please consider replying in linked discussion thread if you don't feel like you are going to vote for any reason. Don't understand what you mean... How about explaining how to vote if it's not here, or there, ... keep things simple please. I am asking for input from those who decided not to vote for some reason. So far activity is rather low and I think I will need some feedback to determine if it is because of low demand or for some other reasons. Maybe because people don't understand the process. It is no different from process used to proceed with std.d.lexer which got 21 vote in smaller time frame. I am especially concerned about lack of votes from Phobos core team.
Re: Gtkd2 in serious use
On Friday, 10 January 2014 at 17:33:31 UTC, Steve Teale wrote: I have done more work on the web page to cut out fluff, and to cover all the composition elements. There is also a beginning for the description of the user interfaces. I lied unwittingly on the web page. I do have the source for the Windows program, but it was in a password protected zip file, and I'd forgotten the password. While checking on it yesterday it suddenly occurred to me what I would have used, and so now I do have it. But there's no way I'm going back to C++.
Re: std.signal : voting has begun
On 2014-01-13 13:50:09 +, Dicebot said: To everyone: please consider replying in linked discussion thread if you don't feel like you are going to vote for any reason. Don't understand what you mean... How about explaining how to vote if it's not here, or there, ... keep things simple please. So far activity is rather low and I think I will need some feedback to determine if it is because of low demand or for some other reasons. Maybe because people don't understand the process. -- Robert M. Münch Saphirion AG http://www.saphirion.com smarter | better | faster
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote: p.s. also, why at first launch it can't just fetch default phobos location for DMD? it's quite annoying adding this paths in settings and it may revolve unaware users from using it(like it was for me about year ago). Okay, implemented it in v1.3
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Monday, 13 January 2014 at 11:49:57 UTC, evilrat wrote: On Monday, 13 January 2014 at 11:03:45 UTC, Alexander Bothe wrote: On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote: after about half year i tried it again on OS X, and Mono-D is quite good for writing the code, but... the debug!!11 can we haz some GDB or LLDB(or both :)) support please? it shouldn't be that hard porting linux code to OS X. it may already doing something useful but it simply doesn't start... I've got no OSX but erm, what tool is required to have lldb information generated? ldc2? On the other side, which tool is then required to get gdb debug info? i don't know about other tools, so basically i just build with "dmd files.d -gc" and debug using console lldb, of course it was mangled but it is better than nothing. Fortunately I implemented demangling already, so that's not a real problem. So according to Jacob's comment it's actually possible to get gdb on OSX - but probably just with a wrong build configuration, i.e. the mi2 interface for gdb is not available - or is it? Just try executing gdb --interpreter=mi2 to see whether Mono-D is able to handle its output properly.
Re: std.signal : voting has begun
To everyone: please consider replying in linked discussion thread if you don't feel like you are going to vote for any reason. So far activity is rather low and I think I will need some feedback to determine if it is because of low demand or for some other reasons.
Re: std.signal : voting has begun
On 2014-01-06 09:11:07 +, Dicebot said: Some time ago there have been a review for `std.signal` Phobos proposal (http://forum.dlang.org/thread/ujlhznaphepibgtpc...@forum.dlang.org#post-ujlhznaphepibgtpcoqz:40forum.dlang.org). It have not received much feedback and I was a it too busy to proceed with final voting at that moment but with no outstanding issues to address nothing prevents that final step. Let's put 2 week deadline to refresh memories about the proposal and make some decision. Voting closes at January 20th 23:59 GMT 0 Please take some time and help make Phobos better ;) Yes. It's a fundamental pattern that should be in Phobos. -- Robert M. Münch Saphirion AG http://www.saphirion.com smarter | better | faster
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On 2014-01-13 12:03, Alexander Bothe wrote: I've got no OSX but erm, what tool is required to have lldb information generated? ldc2? On the other side, which tool is then required to get gdb debug info? With DMD I get the line numbers in a backtrace, both in gdb and lldb. I compiled with -g. You won't get any demangling with lldb or gdb supplied by Apple. -- /Jacob Carlborg
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Monday, 13 January 2014 at 11:03:45 UTC, Alexander Bothe wrote: On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote: after about half year i tried it again on OS X, and Mono-D is quite good for writing the code, but... the debug!!11 can we haz some GDB or LLDB(or both :)) support please? it shouldn't be that hard porting linux code to OS X. it may already doing something useful but it simply doesn't start... I've got no OSX but erm, what tool is required to have lldb information generated? ldc2? On the other side, which tool is then required to get gdb debug info? i don't know about other tools, so basically i just build with "dmd files.d -gc" and debug using console lldb, of course it was mangled but it is better than nothing.
Re: Mono-D v1.2.7 - Completion, ldc2 compatibility, dub fixes
On Monday, 13 January 2014 at 05:25:31 UTC, evilrat wrote: after about half year i tried it again on OS X, and Mono-D is quite good for writing the code, but... the debug!!11 can we haz some GDB or LLDB(or both :)) support please? it shouldn't be that hard porting linux code to OS X. it may already doing something useful but it simply doesn't start... I've got no OSX but erm, what tool is required to have lldb information generated? ldc2? On the other side, which tool is then required to get gdb debug info? p.s. also, why at first launch it can't just fetch default phobos location for DMD? it's quite annoying adding this paths in settings and it may revolve unaware users from using it(like it was for me about year ago). Despite it's clearly explained in the set up guide it sounds quite reasonable to do this automatically, you're right.
