Re: dmd 2.065 beta 2
On 1/26/14, 6:38 PM, Andrew Edwards wrote: Note: There are no RPMs available for Suse and Fedora at the moment. They will be provided upon becoming available. http://ftp.digitalmars.com/dmd-2.065.0~b2-0.openSUSE.x86_64.rpm http://ftp.digitalmars.com/dmd-2.065.0~b2-0.fedora.x86_64.rpm http://ftp.digitalmars.com/dmd-2.065.0~b2-0.openSUSE.i386.rpm http://ftp.digitalmars.com/dmd-2.065.0~b2-0.fedora.i386.rpm Regards, Andrew
Re: dmd 2.065 beta 2
On Sunday, 26 January 2014 at 23:38:56 UTC, Andrew Edwards wrote: We've made a lot of progress towards the 2.065 stable release. Available binaries are as follows: Linux http://ftp.digitalmars.com/dmd.2.065.0-b2.linux.zip For anyone feeling adventurous - I've uploaded an alternative version with the linux64 binary replaced by the linux64 ddmd binary. This is a debug build, with the GC disabled. http://dtsm460.web.cse.unsw.edu.au/dmd.2.065.ddmd.zip
DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
New DCD and DScanner betas are ready for testing. The tags can be found here: https://github.com/Hackerpilot/DCD/tree/0.3.0-beta1 https://github.com/Hackerpilot/Dscanner/tree/0.1.0-beta1 DCD Changes: * Uptake new lexer/parser/ast code from DScanner * Add new --symbolLocation switch that instructs the server to return the declaration location of the symbol at the cursor * Add new --doc switch that instructs the server to return any documentation comments associated with the symbol at the cursor * Fixed #89: Template declarations not included in autocomplete * Fixed #88: Fully qualified names not working * Fixed #82: Unable to generate calltips for methods called on variables * Fixed #79: Unable to build with both DMD and GDC * Fixed #75: Vim plugin doesn't work? DScanner changes: * Now actually tagged with version numbers! * Implemented experimental --styleCheck option that will run some basic static analysis checks on the files provided. ** Warns when opCmp, toHash, toString, and opEquals are not const ** Warns on implicit concatenation of string literals ** Warns on catching the base exception types (i.e Exception, Throwable, etc) ** Warns when the deprecated floating-point operators are used ** Warns when the deprecated delete keyword is used ** Warns when large enum constants such as array literals are created. ** Warns when using old-style alias declarations (i.e. alias type identifier instead of alias identifier = type) ** Warns when using deprecated complex number literals. ** Warns on empty statements (i.e. spare semicolons) ** Warns when using large number literals without underscores ** Warns on violations of the Phobos naming conventions (e.g. mixed case package names, lowercase class names, etc) * Fixed many issues in the parser * Fixed issues with the AST dump not correctly printing several expression node types * Rewrote lexer, parser, and AST code. The new lexer generator should be ready for another Phobos review very soon. About DCD: DCD is the D Completion Daemon, a text editor and IDE-neutral autocompletion engine for the D programming language. DCD has plugins for several editors such as Textadept, Kate, Vim, Emacs, Zeus, and Sublime Text 3. About DScanner: DScanner is a Swiss army knife for D source code. It can perform various tasks such as * Source line of code counting * Import listing * HTML syntax highlighting * Syntax checking * Some basic static analysis * Generating CTAGS * Generating an outline of a D file * Dumping the AST of a D file into an XML file. P.S. Only the Textadept module has support for the new --symbolLocation and --doc switches. If you're one of the excellent people who wrote one of the other plugins, I'd appreciate your help adding support for these features to your favorite editor before a non-beta release is tagged.
Re: New debugger for D!!!
On 2014-01-28 04:00, Sarath Kodali wrote: Next month I will be releasing an alpha version with support for Linux, x86, Elf+Dwarf, DMD and GCC. I'm waiting for the OS X version :) But in the coming months I will add support for other 64 bit OSes and compilers. I'm also planning to add a JSON or CSV output format so that it will be easy to parse the output when integrating with IDEs. Why not make it useable as a library that can be directly integrated into an IDE. -- /Jacob Carlborg
Re: dmd 2.065 beta 2
On 2014-01-28 09:19, Daniel Murphy wrote: For anyone feeling adventurous - I've uploaded an alternative version with the linux64 binary replaced by the linux64 ddmd binary. This is a debug build, with the GC disabled. http://dtsm460.web.cse.unsw.edu.au/dmd.2.065.ddmd.zip Cool. Is it too early to try it on OS X? -- /Jacob Carlborg
Re: dmd 2.065 beta 2
Jacob Carlborg wrote in message news:lc7vah$149c$2...@digitalmars.com... Cool. Is it too early to try it on OS X? It's ~4 hours work away from working on OS X (if the linux port is a good indicator), but I don't have a mac box to work on. If anyone can provide me with an ssh account I'd be happy to produce an OS X version.
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 10:03:03 UTC, Jacob Carlborg wrote: On 2014-01-28 04:00, Sarath Kodali wrote: Next month I will be releasing an alpha version with support for Linux, x86, Elf+Dwarf, DMD and GCC. I'm waiting for the OS X version :) not going happen until dmd gets fixed. i'm not tested GDC yet, but others compilers don't emit variable address info for debug or it shown as optimized out values. i think it may be related to TLS because __gshared variables CAN be debugged.
Re: New debugger for D!!!
On 28 January 2014 13:24, evilrat evilrat...@gmail.com wrote: On Tuesday, 28 January 2014 at 10:03:03 UTC, Jacob Carlborg wrote: On 2014-01-28 04:00, Sarath Kodali wrote: Next month I will be releasing an alpha version with support for Linux, x86, Elf+Dwarf, DMD and GCC. I'm waiting for the OS X version :) not going happen until dmd gets fixed. i'm not tested GDC yet, but others compilers don't emit variable address info for debug or it shown as optimized out values. i think it may be related to TLS because __gshared variables CAN be debugged. 1) If it's optimised out then I suggest not running a debugger with -O generated code. 2) What debugger are you using? I am aware that gdb does not evaluate D programs correctly in certain situations.
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 13:59:48 UTC, Iain Buclaw wrote: On 28 January 2014 13:24, evilrat evilrat...@gmail.com wrote: On Tuesday, 28 January 2014 at 10:03:03 UTC, Jacob Carlborg wrote: On 2014-01-28 04:00, Sarath Kodali wrote: Next month I will be releasing an alpha version with support for Linux, x86, Elf+Dwarf, DMD and GCC. I'm waiting for the OS X version :) not going happen until dmd gets fixed. i'm not tested GDC yet, but others compilers don't emit variable address info for debug or it shown as optimized out values. i think it may be related to TLS because __gshared variables CAN be debugged. 1) If it's optimised out then I suggest not running a debugger with -O generated code. it is optimized out with LDC compiled program, and simply not present with DMD. 2) What debugger are you using? I am aware that gdb does not evaluate D programs correctly in certain situations. both gdb and llvm. results are same.
Re: David Nadlinger (klickverbot) gets $150 bounty
On Tuesday, 28 January 2014 at 06:49:53 UTC, Andrei Alexandrescu wrote: Please join me in congratulating David! *envious*
Re: New debugger for D!!!
On Monday, 27 January 2014 at 16:42:14 UTC, Sarath Kodali wrote: p1.1 SUSPENDED [D main in dbg.d] 179: auto cmd = new Command(uiType); dbg step -o p1.1 STEPPED [D main in dbg.d] 180: cmd.rc_exec(GLOBAL_DBGRC_FILE); Would you mind putting the line number in the same line as the file name? I'm working on a debugger plugin for Vim, and I would obviously want to support your debugger once it's released. I find it easy to interpret the debugger output line by line, and it really makes things hard when I have to join data from multiple lines... You said you want to add JSON and\or CSV output formats, Vim doesn't support JSON natively and CSV is still multiple lines. So, if it wouldn't be too hard having data in the same line can be really be helpful! This is also true when printing values - having the expression and the result printed at the same line makes things easier to interpret. BTW, would you mind picking a different name? I understand that dbg stands for D Debugger, but there is already a debugger named dbg(http://www.php-debugger.com/dbg/) and with a name so generic I would be surprised if there aren't other debuggers with that name...
Re: New debugger for D!!!
On 28 January 2014 14:14, evilrat evilrat...@gmail.com wrote: On Tuesday, 28 January 2014 at 13:59:48 UTC, Iain Buclaw wrote: On 28 January 2014 13:24, evilrat evilrat...@gmail.com wrote: On Tuesday, 28 January 2014 at 10:03:03 UTC, Jacob Carlborg wrote: On 2014-01-28 04:00, Sarath Kodali wrote: Next month I will be releasing an alpha version with support for Linux, x86, Elf+Dwarf, DMD and GCC. I'm waiting for the OS X version :) not going happen until dmd gets fixed. i'm not tested GDC yet, but others compilers don't emit variable address info for debug or it shown as optimized out values. i think it may be related to TLS because __gshared variables CAN be debugged. 1) If it's optimised out then I suggest not running a debugger with -O generated code. it is optimized out with LDC compiled program, and simply not present with DMD. This sounds promising for GDC (I'm yet to come across some that is along the lines of what you describe).
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 15:23:28 UTC, Idan Arye wrote: On Monday, 27 January 2014 at 16:42:14 UTC, Sarath Kodali wrote: BTW, would you mind picking a different name? I understand that dbg stands for D Debugger, but there is already a debugger named dbg(http://www.php-debugger.com/dbg/) and with a name so generic I would be surprised if there aren't other debuggers with that name... In the event that you take Idan's advice, I just want to be the first to come up with a lame naming suggestion. smackD I thought I was being very original with that one, but of course there is already a similarly named product used for Java in Eclipse: http://blog.teamextension.com/smack-enhanced-debugger-1278 but not being a Java person I have no idea if that is a popular product at all.
Re: dmd 2.065 beta 2
DDMD alpha win32 debug nogc http://dtsm460.web.cse.unsw.edu.au/dmd.2.065.0-b2.windows.ddmd.zip This one is most likely to work!
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 05:19:13 UTC, Andrei Alexandrescu wrote: This does sound very interesting - and don't forget to submit a talk on the topic to DConf!!! Andrei Can't commit but will try :( too many things in my hand ...
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 10:03:03 UTC, Jacob Carlborg wrote: On 2014-01-28 04:00, Sarath Kodali wrote: Next month I will be releasing an alpha version with support for Linux, x86, Elf+Dwarf, DMD and GCC. I'm waiting for the OS X version :) But in the coming months I will add support for other 64 bit OSes and compilers. I'm also planning to add a JSON or CSV output format so that it will be easy to parse the output when integrating with IDEs. Why not make it useable as a library that can be directly integrated into an IDE. If dbg is a library, whenever the debugger hangs or crashes, the IDE also hangs or crashes and you may loose all your data. It is much safer to have dbg as a server and have an IDE plugin as a client.
Re: New debugger for D!!!
Am 28.01.2014 17:24, schrieb dennis luehring: Am 28.01.2014 17:16, schrieb Sarath Kodali: I expect this is how it will be even with dbg and IDEs. The IDE will have a plugin that sits between the debugger and IDE. The communication between the IDE plugin and debugger will be over a socket and the dbg output will be in JSON format so that IDE plugin can parse it properly. Depending on the IDE, the plugin will be either a library (dll) or an independent executable. its a little bit different to pin because pin is the host of the given tool-communication dll - so the dll interface is the interface not JSON (pin(tool dll--)-- any protocol -- ide/whatever in your idea dbg --- socker/JASON -- ide/whatever the question is - debuggers needs to throw masses of information around - why put a slow JSON parser between, every single step command gets JSONed, parsed, singlestep, result gets JSOned etc... millions of times - why? i would suggest an real tool api for loaded protocol-drivers - like pin do - and implement a control_dbg_with_tcp_and_json.dll as a driver this way its still possible to build a super fast tracing server on top of dbg - else JSON will become a problem - without any need because the same target is reachable with a driver-dll(plugin)
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 06:34:50 UTC, dennis luehring wrote: Am 28.01.2014 04:00, schrieb Sarath Kodali: I'm also planning to add a JSON or CSV output format so that it will be easy to parse the output when integrating with IDEs. So I would recommend that you wait till I release 1.0 version - sometime before Dconf 2014 - hopefully! why don't ease the IDE integration even more - for example the pin tool from intel (ptools.org) is a normal executable (the server) but you can give pin a tool/commander dll per commandline which is then responsible for controling the debugger - this way its very easy to integrate the debugger into any environment fast and performant examples pin.exe -t idadbg.dll - starts pin with an IDA-tool-dll to be able to control pin with the ida debugger pin.exe -t vsdbg.dll - starts pin with an vs-studio debug helper this way you can use pin as an debugger for VStudio etc. csv and json is nice - but there a much nicer ways of doing ipc I expect this is how it will be even with dbg and IDEs. The IDE will have a plugin that sits between the debugger and IDE. The communication between the IDE plugin and debugger will be over a socket and the dbg output will be in JSON format so that IDE plugin can parse it properly. Depending on the IDE, the plugin will be either a library (dll) or an independent executable.
Re: New debugger for D!!!
Am 28.01.2014 17:16, schrieb Sarath Kodali: I expect this is how it will be even with dbg and IDEs. The IDE will have a plugin that sits between the debugger and IDE. The communication between the IDE plugin and debugger will be over a socket and the dbg output will be in JSON format so that IDE plugin can parse it properly. Depending on the IDE, the plugin will be either a library (dll) or an independent executable. its a little bit different to pin because pin is the host of the given tool-communication dll - so the dll interface is the interface not JSON (pin(tool dll--)-- any protocol -- ide/whatever in your idea dbg --- socker/JASON -- ide/whatever the question is - debuggers needs to throw masses of information around - why put a slow JSON parser between, every single step command gets JSONed, parsed, singlestep, result gets JSOned etc... millions of times - why?
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 15:23:28 UTC, Idan Arye wrote: On Monday, 27 January 2014 at 16:42:14 UTC, Sarath Kodali wrote: p1.1 SUSPENDED [D main in dbg.d] 179: auto cmd = new Command(uiType); dbg step -o p1.1 STEPPED [D main in dbg.d] 180: cmd.rc_exec(GLOBAL_DBGRC_FILE); Would you mind putting the line number in the same line as the file name? I'm working on a debugger plugin for Vim, and I would obviously want to support your debugger once it's released. I find it easy to interpret the debugger output line by line, and it really makes things hard when I have to join data from multiple lines... You said you want to add JSON and\or CSV output formats, Vim doesn't support JSON natively and CSV is still multiple lines. So, if it wouldn't be too hard having data in the same line can be really be helpful! This is also true when printing values - having the expression and the result printed at the same line makes things easier to interpret. The output is configurable, independent of JSON or CSV, and this is just one form. I will make it as easy of possible for plug-ins to parse the output. BTW, would you mind picking a different name? I understand that dbg stands for D Debugger, but there is already a debugger named dbg(http://www.php-debugger.com/dbg/) and with a name so generic I would be surprised if there aren't other debuggers with that name... I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. - Sarath
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 16:24:32 UTC, dennis luehring wrote: Am 28.01.2014 17:16, schrieb Sarath Kodali: I expect this is how it will be even with dbg and IDEs. The IDE will have a plugin that sits between the debugger and IDE. The communication between the IDE plugin and debugger will be over a socket and the dbg output will be in JSON format so that IDE plugin can parse it properly. Depending on the IDE, the plugin will be either a library (dll) or an independent executable. its a little bit different to pin because pin is the host of the given tool-communication dll - so the dll interface is the interface not JSON (pin(tool dll--)-- any protocol -- ide/whatever in your idea dbg --- socker/JASON -- ide/whatever the question is - debuggers needs to throw masses of information around - why put a slow JSON parser between, every single step command gets JSONed, parsed, singlestep, result gets JSOned etc... millions of times - why? I'm not fixated on JSON :) I thought that is more popular now-a-days :). Today dbg outputs in human readable format. After the alpha release, I will add the machine readable format - what everyone prefers.
Re: New debugger for D!!!
Am 28.01.2014 18:23, schrieb Sarath Kodali: the question is - debuggers needs to throw masses of information around - why put a slow JSON parser between, every single step command gets JSONed, parsed, singlestep, result gets JSOned etc... millions of times - why? I'm not fixated on JSON:) I thought that is more popular now-a-days:). Today dbg outputs in human readable format. After the alpha release, I will add the machine readable format - what everyone prefers. clear - i would just use a plugin system for adding json or whatever communication (like pin do) so its still api based - not (text/binary) protocol based from the very beginning
Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
On Tuesday, 28 January 2014 at 09:58:27 UTC, Brian Schott wrote: New DCD and DScanner betas are ready for testing. The tags can be found here: https://github.com/Hackerpilot/DCD/tree/0.3.0-beta1 https://github.com/Hackerpilot/Dscanner/tree/0.1.0-beta1 DCD Changes: * Uptake new lexer/parser/ast code from DScanner * Add new --symbolLocation switch that instructs the server to return the declaration location of the symbol at the cursor * Add new --doc switch that instructs the server to return any documentation comments associated with the symbol at the cursor * Fixed #89: Template declarations not included in autocomplete * Fixed #88: Fully qualified names not working * Fixed #82: Unable to generate calltips for methods called on variables * Fixed #79: Unable to build with both DMD and GDC * Fixed #75: Vim plugin doesn't work? DScanner changes: * Now actually tagged with version numbers! * Implemented experimental --styleCheck option that will run some basic static analysis checks on the files provided. ** Warns when opCmp, toHash, toString, and opEquals are not const ** Warns on implicit concatenation of string literals ** Warns on catching the base exception types (i.e Exception, Throwable, etc) ** Warns when the deprecated floating-point operators are used ** Warns when the deprecated delete keyword is used ** Warns when large enum constants such as array literals are created. ** Warns when using old-style alias declarations (i.e. alias type identifier instead of alias identifier = type) ** Warns when using deprecated complex number literals. ** Warns on empty statements (i.e. spare semicolons) ** Warns when using large number literals without underscores ** Warns on violations of the Phobos naming conventions (e.g. mixed case package names, lowercase class names, etc) * Fixed many issues in the parser * Fixed issues with the AST dump not correctly printing several expression node types * Rewrote lexer, parser, and AST code. The new lexer generator should be ready for another Phobos review very soon. About DCD: DCD is the D Completion Daemon, a text editor and IDE-neutral autocompletion engine for the D programming language. DCD has plugins for several editors such as Textadept, Kate, Vim, Emacs, Zeus, and Sublime Text 3. About DScanner: DScanner is a Swiss army knife for D source code. It can perform various tasks such as * Source line of code counting * Import listing * HTML syntax highlighting * Syntax checking * Some basic static analysis * Generating CTAGS * Generating an outline of a D file * Dumping the AST of a D file into an XML file. P.S. Only the Textadept module has support for the new --symbolLocation and --doc switches. If you're one of the excellent people who wrote one of the other plugins, I'd appreciate your help adding support for these features to your favorite editor before a non-beta release is tagged. You're work is filling an important gap. Thanks. I have just finished updating Sublime Text 3 plugin to use Goto Definition feature. But I'm still wondering on how to approach the documentation preview feature as Sublime doesn't provide much. https://github.com/yazd/DKit
Re: New debugger for D!!!
On 01/28/2014 12:00 PM, Sarath Kodali wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. bugD :)
Re: New debugger for D!!!
On 1/28/2014 12:15 PM, Jacob Carlborg wrote: On 2014-01-28 17:21, Sarath Kodali wrote: If dbg is a library, whenever the debugger hangs or crashes, the IDE also hangs or crashes and you may loose all your data. It is much safer to have dbg as a server and have an IDE plugin as a client. Fair enough. JSON still doesn't sound like a very effective way to communicate with. Yea, I'd strongly recommend using a proper binary format. Protobuf can help with that. Text-based data is overused, overrated, and completely pointless for direct software-software communication (as opposed to human-software or software-human).
Re: New debugger for D!!!
On Tuesday, 28 January 2014 at 22:04:34 UTC, John J wrote: On 01/28/2014 12:00 PM, Sarath Kodali wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. bugD :) buggeD?
Re: New debugger for D!!!
I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. - Sarath D!buger
Re: New debugger for D!!!
On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. - Sarath D!buger Too complicated, keep it simple. Maybe Dug, which stands for D Debug.
Re: dmd 2.065 beta 2
I had an issue with the windows installer. It didn't remember where my existing D installation was, and tried to installer it somewhere else by default. It should remember where I installed it last time and upgrade the existing installation. On 27 January 2014 10:38, Andrew Edwards rid...@yahoo.com wrote: We've made a lot of progress towards the 2.065 stable release. Available binaries are as follows: All Systems http://ftp.digitalmars.com/dmd.2.065.0-b2.zip FreeBSD http://ftp.digitalmars.com/dmd.2.065.0-b2.freebsd-32.zip http://ftp.digitalmars.com/dmd.2.065.0-b2.freebsd-64.zip Linux http://ftp.digitalmars.com/dmd.2.065.0-b2.linux.zip http://ftp.digitalmars.com/dmd_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/dmd_2.065.0-b2-0_i386.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_i386.deb OSX http://ftp.digitalmars.com/dmd.2.065.0-b2.osx.zip http://ftp.digitalmars.com/dmd.2.065.0-b2.dmg Windows http://ftp.digitalmars.com/dmd.2.065.0-b2.exe http://ftp.digitalmars.com/dmd.2.065.0-b2.windows.zip Note: There are no RPMs available for Suse and Fedora at the moment. They will be provided upon becoming available. The list of current regressions may be accessed here: http://d.puremagic.com/issues/buglist.cgi?query_format= advancedbug_severity=regressionbug_status=NEWbug_ status=ASSIGNEDbug_status=REOPENED Following are the changes incorporated since beta 1: DMD Issue 11982 - ICE(func.c) With function literal with no body Issue 11974 - ICE(case.c) Segfault with invalid assignment Issue 11966 - inout(const(char))[] doesn't convert to inout(char)[] Issue 11956 - dmd doesn't lookup /etc/dmd.conf Issue 11968 - ICE(expression.c) Crash when deleting __FILE__ Issue 11944 - ICE(expression.c) Assertion `f' failed. Issue 11922 - ICE on nonexistent identifier in templated auto method Issue 11924 - inout Variadic Template Parameters Issue 11896 - isVirtualMethod related GitHub HEAD regression (works with 2.064) Issue 11930 - Alias this not considered in is(T unused: U) matching Issue 11931 - Linkers Symbol Undefined again with dmd HEAD when -g specified Issue 11941 - Errors when appending to aggregate member array in CTFE Issue 11967 - ICE(parse.c) Parser crash Issue 11965 - Segfault on garbage Issue 11963 - ICE(parse.c) Parser crash Druntime None Phobos Remove duplicate ArchiveMember.madeVersion() property. Rename phobos.html = index.html Installer Pull #44 - Build the installer GUI for D2 on OS X Pull #43 - add dustmite binary on deb/rpm packages Pull #42 - don't zip .git* and .DS_Store files Pull #41 - fix expanding zip files created on Windows Pull #40 - cleanup leftover from merge conflict dlang.org Pull #480 - fix chmgen after renaming phobos.html = index.html Pull #478 - Revert changelog.dd encoding to UTF-8 Pull #477 - Changelog: add notes about std.uni.byGrapheme and std.range.only Pull #476 - 2.065 changelog tools None Regards, Andrew
Re: New debugger for D!!!
On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. - Sarath D!buger ! is not a valid character for filenames, and that can be a problem when you want to... you know... name the executable. It can always be named Dbangbugger, but that's a bit cumbersome... maybe Dbanger? Eh... probably not a good idea...
Re: New debugger for D!!!
On Monday, 27 January 2014 at 16:42:14 UTC, Sarath Kodali wrote: I'm planning to release a new debugger for D sometime during end of February. This is a heads up for all those who are eagerly looking for a good debugger for D. Here is a sample debug session: Do you know ngdb (https://github.com/MartinNowak/ngdb)? It might be helpful for your implementation.
Re: New debugger for D!!!
On 01/28/2014 06:04 PM, Francesco Cattoglio wrote: On Tuesday, 28 January 2014 at 22:04:34 UTC, John J wrote: On 01/28/2014 12:00 PM, Sarath Kodali wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. bugD :) buggeD? Yes, the bugD pronounced as bugged! :)
D bindings for Shapefile C Library
I've created bindings for the C Shapefile Library. Shapefiles are a format used commonly in vector based Geographic Information Systems, often for data interchange. It is a pretty simple library and it is my first effort at creating such bindings. https://github.com/craig-dillabaugh/shplib.d I've looked in Demios and code.dlang.org to see what the standard setup for such bindings is, and while most are similar there doesn't seem to be an accepted layout. If anyone has a moment to spare I would be happy if someone could have a look to see if there are any obvious improvements that should be made. I plan to run a few more tests on my bindings, and once those all work, I hope to add this to code.dlang.org.
Re: dmd 2.065 beta 2
On Wednesday, 29 January 2014 at 00:41:46 UTC, Manu wrote: I had an issue with the windows installer. It didn't remember where my existing D installation was, and tried to installer it somewhere else by default. It should remember where I installed it last time and upgrade the existing installation. The Window installer here doesn't actually work because the URL is wrong. You're just using your previous installation.
Re: dmd 2.065 beta 2
On 29 January 2014 15:33, Brad Anderson e...@gnuk.net wrote: On Wednesday, 29 January 2014 at 00:41:46 UTC, Manu wrote: I had an issue with the windows installer. It didn't remember where my existing D installation was, and tried to installer it somewhere else by default. It should remember where I installed it last time and upgrade the existing installation. The Window installer here doesn't actually work because the URL is wrong. You're just using your previous installation. Interesting. I thought it 'installed' abnormally quickly... :)
Re: D bindings for Shapefile C Library
Big thanks! Could you provide simple example of usage this lib. I have not experience in usage bindings, but I would like to try to write some tiny app to working with shp files.
Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
Could you help me with installation of Sublime plugin. I can't find menu: Preferences - Package Settings - DKit - Settings - User in Sublime interface.
Re: dmd 2.065 beta 2
On Sunday, 26 January 2014 at 23:38:56 UTC, Andrew Edwards wrote: Linux http://ftp.digitalmars.com/dmd.2.065.0-b2.linux.zip http://ftp.digitalmars.com/dmd_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/dmd_2.065.0-b2-0_i386.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_i386.deb 502 bad gateway :(
Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
Oh! That's my issue!
Re: New debugger for D!!!
On Wednesday, 29 January 2014 at 01:13:12 UTC, Martin Nowak wrote: On Monday, 27 January 2014 at 16:42:14 UTC, Sarath Kodali wrote: I'm planning to release a new debugger for D sometime during end of February. This is a heads up for all those who are eagerly looking for a good debugger for D. Here is a sample debug session: Do you know ngdb (https://github.com/MartinNowak/ngdb)? It might be helpful for your implementation. Thanks for the link, I will take a look. Is this a working debugger? - Sarath
Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
Look like I was need to write C:\\D\\dmd2\\windows\\bin\\ instead of C:\\D\\dmd2\\windows\\bin Thanks! All work!
Re: D bindings for Shapefile C Library
On Wednesday, 29 January 2014 at 05:12:45 UTC, Rikki Cattermole wrote: For simple static bindings, it looks fine. You'll probably have fun getting it to work on Windows 32 bit though. Thank you OMF. what fun? using (coff)implib once? come on, that's not that hard at all... the only fun is when lib export only constants which is rare.
Re: dmd 2.065 beta 2
On Wednesday, 29 January 2014 at 06:33:27 UTC, deadalnix wrote: On Sunday, 26 January 2014 at 23:38:56 UTC, Andrew Edwards wrote: Linux http://ftp.digitalmars.com/dmd.2.065.0-b2.linux.zip http://ftp.digitalmars.com/dmd_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/dmd_2.065.0-b2-0_i386.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_i386.deb 502 bad gateway :( All links work here. Try clearing your browser cache.
Re: New debugger for D!!!
+1. Same name I thought of :) On Wed, Jan 29, 2014 at 2:26 AM, Meta jared...@gmail.com wrote: On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. - Sarath D!buger Too complicated, keep it simple. Maybe Dug, which stands for D Debug.
Re: New debugger for D!!!
On 1/28/14 4:26 PM, Meta wrote: On Wednesday, 29 January 2014 at 00:07:00 UTC, Namespace wrote: I did not do any research on name; just shortened debug to dbg :) I'm bad at coming up with good names, so any suggestions are always welcome. - Sarath D!buger Too complicated, keep it simple. Maybe Dug, which stands for D Debug. noice
Re: New debugger for D!!!
On 1/28/14 8:04 AM, Sarath Kodali wrote: On Tuesday, 28 January 2014 at 05:19:13 UTC, Andrei Alexandrescu wrote: This does sound very interesting - and don't forget to submit a talk on the topic to DConf!!! Andrei Can't commit but will try :( too many things in my hand ... Do it. http://www.youtube.com/watch?v=JoqDYcCDOTg Andrei
Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
For thous who very lazy to build Sublime integration manually I would like suggest ready to use package. Gust unzip and fix paths (if needed) http://dynamic.dlang.ru/Files/2014/Sublime-D-integration-plugin-29-01-2014.zip
LDC 0.13.0 alpha released! Please help test!
Hi everyone, LDC 0.13.0-alpha1, the LLVM-based D compiler, is available for download! This is the first alpha release based on the 2.064.2 frontend and standard library and supports LLVM 3.1-3.4 (OS X: 3.2/3.4 only). Please help testing this release! As usual, you can find links to the changelog and the binary packages over at digitalmars.D.ldc: http://forum.dlang.org/thread/csgcsrniyaylxufbh...@forum.dlang.org#post-csgcsrniyaylxufbhiux:40forum.dlang.org Regards, Kai
Re: dmd 2.065 beta 2
On Wednesday, 29 January 2014 at 07:02:08 UTC, Andrew Edwards wrote: On Wednesday, 29 January 2014 at 06:33:27 UTC, deadalnix wrote: On Sunday, 26 January 2014 at 23:38:56 UTC, Andrew Edwards wrote: Linux http://ftp.digitalmars.com/dmd.2.065.0-b2.linux.zip http://ftp.digitalmars.com/dmd_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/dmd_2.065.0-b2-0_i386.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_amd64.deb http://ftp.digitalmars.com/libphobos2-65_2.065.0-b2-0_i386.deb 502 bad gateway :( All links work here. Try clearing your browser cache. Awesome, that compile my code and test suite are passing. Everything looks good !
Re: DCD 0.3.0-beta1 and DScanner 0.1.0-beta1
On Wednesday, 29 January 2014 at 06:53:34 UTC, Suliman wrote: Look like I was need to write C:\\D\\dmd2\\windows\\bin\\ instead of C:\\D\\dmd2\\windows\\bin Thanks! All work! That's weird. Anyway, if you would like to help with Windows setup, please submit your difficulties in a pull request to update the README, or point in them in the issue tracker on github as I have not personally run the plugin on a Windows machine.
