Re: FancyPars
On Wednesday, 16 September 2015 at 12:16:03 UTC, Bastiaan Veelo wrote: Sounds like you want to share this, but I can't find a licence. In case this turns out to be useful, we would need one :-) If you want I can prepare a PR for that, just let me know which licence to pick. Best, Bastiaan. I am not sure. The source should not be used in any product without my explicit permission. However you may study it to get better in your understanding of dlang or parser technology
Re: LDC 0.16.0 alpha3 is out! Get it, test it, give feedback!
On Thursday, 17 September 2015 at 15:19:07 UTC, John Colvin wrote: dub build --compiler=ldc2 -v will sometimes let you see more clearly when/where things went wrong. Seems to be a segfault in LDC $ dub build --force --compiler=ldc2 -v A bunch of stuff for the dependancies Using direct -l... flags for dl. Running ldc2... ldc2 -of.dub/build/application-debug-posix.osx-x86_64-ldc_0-C7E5B672CD1184CE7A0D4F80B1606A44/dungeon -d-debug -g -w -oq -od=.dub/obj -d-version=Have_dungeon -d-version=Have_dgame -d-version=Have_derelict_sdl2 -d-version=Have_derelict_util -d-version=Have_derelict_gl3 -Isource/ -I../../../../.dub/packages/dgame-0.6.3/source/ -I../../../../.dub/packages/derelict-sdl2-1.9.7/source/ -I../../../../.dub/packages/derelict-util-2.0.3/source/ -I../../../../.dub/packages/derelict-gl3-1.0.15/source/ source/app.d source/engine.d source/enums.d source/inputhandler.d source/interfaces.d source/objects/enemies.d source/objects/player.d source/states/endgame.d source/states/game.d source/states/main_menu.d source/surfaces.d source/util/quadtree.d source/util/ringbuffer.d ../../../../.dub/packages/dgame-0.6.3/lib/libDgame.a ../../../../.dub/packages/derelict-sdl2-1.9.7/lib/libDerelictSDL2.a ../../../../.dub/packages/derelict-gl3-1.0.15/lib/libDerelictGL3.a ../../../../.dub/packages/derelict-util-! 2.0.3/lib/libDerelictUtil.a -L=-ldl FAIL .dub/build/application-debug-posix.osx-x86_64-ldc_0-C7E5B672CD1184CE7A0D4F80B1606A44/ dungeon executable Error executing command build: ldc2 failed with exit code -11. So I manually copied the command from dub to see what went wrong $ ldc2 -of.dub/build/application-debug-posix.osx-x86_64-ldc_0-C7E5B672CD1184CE7A0D4F80B1606A44/dungeon -d-debug -g -w -oq -od=.dub/obj -d-version=Have_dungeon -d-version=Have_dgame -d-version=Have_derelict_sdl2 -d-version=Have_derelict_util -d-version=Have_derelict_gl3 -Isource/ -I../../../../.dub/packages/dgame-0.6.3/source/ -I../../../../.dub/packages/derelict-sdl2-1.9.7/source/ -I../../../../.dub/packages/derelict-util-2.0.3/source/ -I../../../../.dub/packages/derelict-gl3-1.0.15/source/ source/app.d source/engine.d source/enums.d source/inputhandler.d source/interfaces.d source/objects/enemies.d source/objects/player.d source/states/endgame.d source/states/game.d source/states/main_menu.d source/surfaces.d source/util/quadtree.d source/util/ringbuffer.d ../../../../.dub/packages/dgame-0.6.3/lib/libDgame.a ../../../../.dub/packages/derelict-sdl2-1.9.7/lib/libDerelictSDL2.a ../../../../.dub/packages/derelict-gl3-1.0.15/lib/libDerelictGL3.a ../../../../.dub/packages/derelict-util-! 2.0.3/lib/libDerelictUtil.a -L=-ldl [1]45808 segmentation fault ldc2 -d-debug -g -w -oq -od=.dub/obj -d-version=Have_dungeon -Isource/
Re: FancyPars
On Wednesday, 16 September 2015 at 21:25:40 UTC, Bastiaan Veelo wrote: Thanks. At first I thought that fancy_[ast|token|lexer|parser|printer].d were generated files because their content is so similar to the code produced in the vibe application. But on closer look I think it is the other way around: that the example grammar in vibe describes its own input format, and that the similarity in the produced output to said files is an illustration that it works the way it should. Am I close? fancyPars has gone through a few iterations. I used fancyPars to generate a parser for itself and then fixed up the things that fancyPars cannot yet generate. I eat my own dogfood! Thanks for the pascal specs and your p2d.d I will see what I can do about that.
Re: FancyPars
On Thursday, 17 September 2015 at 16:02:14 UTC, John Colvin wrote: Yikes. Are you sure? Are you familiar with open source licensing? I would be open to open-source the "base" of fp. but keeping certin extentions for grammar analysis closed. What license would you suggest for that.
Re: LDC 0.16.0 alpha3 is out! Get it, test it, give feedback!
On Thursday, 17 September 2015 at 15:15:33 UTC, Jack Stouffer wrote: My dub build is failing with LDC but working with DMD. All I get is this unhelpful error message $ dub build --compiler=ldc2 Target derelict-util 2.0.3 is up to date. Use --force to rebuild. Building derelict-sdl2 1.9.7 configuration "library", build type debug. Running ldc2... Target derelict-gl3 1.0.15 is up to date. Use --force to rebuild. Building dgame 0.6.3 configuration "lib", build type debug. Running ldc2... Building dungeon ~master configuration "application", build type debug. Running ldc2... FAIL .dub/build/application-debug-posix.osx-x86_64-ldc_0-C7E5B672CD1184CE7A0D4F80B1606A44/ dungeon executable Error executing command build: ldc2 failed with exit code -11. How does one debug dub builds? dub build --compiler=ldc2 -v will sometimes let you see more clearly when/where things went wrong.
Re: LDC 0.16.0 alpha3 is out! Get it, test it, give feedback!
On 9/17/15 8:15 AM, Jack Stouffer wrote: Building dungeon ~master ... Forgive the unhelpful reply, but this line made me happy :)
Re: FancyPars
On Thursday, 17 September 2015 at 15:47:42 UTC, Stefan Koch wrote: On Wednesday, 16 September 2015 at 12:16:03 UTC, Bastiaan Veelo wrote: Sounds like you want to share this, but I can't find a licence. In case this turns out to be useful, we would need one :-) If you want I can prepare a PR for that, just let me know which licence to pick. Best, Bastiaan. I am not sure. The source should not be used in any product without my explicit permission. However you may study it to get better in your understanding of dlang or parser technology Yikes. Are you sure? Are you familiar with open source licensing?
Re: LDC 0.16.0 alpha3 is out! Get it, test it, give feedback!
On Wednesday, 16 September 2015 at 20:03:15 UTC, Kai Nacke wrote: Hi everyone, LDC 0.16.0 alpha3, the LLVM-based D compiler, is available for download! Is there anyway to get dub to use this as a compiler so I can test this out?
Re: LDC 0.16.0 alpha3 is out! Get it, test it, give feedback!
On Thursday, 17 September 2015 at 14:51:32 UTC, Jack Stouffer wrote: On Wednesday, 16 September 2015 at 20:03:15 UTC, Kai Nacke wrote: Hi everyone, LDC 0.16.0 alpha3, the LLVM-based D compiler, is available for download! Is there anyway to get dub to use this as a compiler so I can test this out? My dub build is failing with LDC but working with DMD. All I get is this unhelpful error message $ dub build --compiler=ldc2 Target derelict-util 2.0.3 is up to date. Use --force to rebuild. Building derelict-sdl2 1.9.7 configuration "library", build type debug. Running ldc2... Target derelict-gl3 1.0.15 is up to date. Use --force to rebuild. Building dgame 0.6.3 configuration "lib", build type debug. Running ldc2... Building dungeon ~master configuration "application", build type debug. Running ldc2... FAIL .dub/build/application-debug-posix.osx-x86_64-ldc_0-C7E5B672CD1184CE7A0D4F80B1606A44/ dungeon executable Error executing command build: ldc2 failed with exit code -11. How does one debug dub builds?
Re: LDC 0.16.0 alpha3 is out! Get it, test it, give feedback!
On Thursday, 17 September 2015 at 14:51:32 UTC, Jack Stouffer wrote: On Wednesday, 16 September 2015 at 20:03:15 UTC, Kai Nacke wrote: Hi everyone, LDC 0.16.0 alpha3, the LLVM-based D compiler, is available for download! Is there anyway to get dub to use this as a compiler so I can test this out? Put the compiler in your PATH, and use the --compiler=ldc2 flag in DUB
Re: FancyPars
On Thursday, 17 September 2015 at 16:33:12 UTC, Stefan Koch wrote: On Thursday, 17 September 2015 at 16:02:14 UTC, John Colvin wrote: Yikes. Are you sure? Are you familiar with open source licensing? I would be open to open-source the "base" of fp. but keeping certin extentions for grammar analysis closed. What license would you suggest for that. Assuming you wrote it all, you can license the code in whatever way you want. See http://choosealicense.com for more info. You can even use multiple licenses, or different licenses for different parts of the code.
Re: FancyPars
On Thursday, 17 September 2015 at 16:55:42 UTC, John Colvin wrote: Assuming you wrote it all, you can license the code in whatever way you want. See http://choosealicense.com for more info. You can even use multiple licenses, or different licenses for different parts of the code. Hmm reading this. No license, is best for now. @Bastian The FancyPars Grammar for pascal will look very very different from what you wrote. In FancyPars Grammars I worked very hard to avoid repetitions. FGPs do not just describe the language grammar. They are describing the AST-Structure. So just by reading the grammar a person working with the AST will know what is what and in which members-variables of the AST-Node which information is stored. I would recommed you open issues in the FancyPars-repo for stuff that is hard to understand.
dfmt 0.4.0
https://github.com/Hackerpilot/dfmt https://github.com/Hackerpilot/dfmt/releases/tag/v0.4.0 https://github.com/Hackerpilot/dfmt/issues?q=milestone%3A0.4.0+is%3Aclosed dfmt is a formatter for D source code. Version 0.4.0 includes a few minor features such as "//dfmt off" and "//dfmt on" comments as well as a lot of bug fixes.
Re: FancyPars
On Thursday, 17 September 2015 at 20:32:59 UTC, Stefan Koch wrote: On Thursday, 17 September 2015 at 16:55:42 UTC, John Colvin wrote: Assuming you wrote it all, you can license the code in whatever way you want. See http://choosealicense.com for more info. You can even use multiple licenses, or different licenses for different parts of the code. Hmm reading this. No license, is best for now. Take your time, but without a license anyone cloning or forking your repo is in fact violating your copyright. It is not what most people expect on github, and I will have to delete my fork and local clone... @Bastiaan The FancyPars Grammar for pascal will look very very different from what you wrote. In FancyPars Grammars I worked very hard to avoid repetitions. FGPs do not just describe the language grammar. They are describing the AST-Structure. So just by reading the grammar a person working with the AST will know what is what and in which members-variables of the AST-Node which information is stored. I can see the value of that when designing a grammar, or building a translator. In my case though the grammar was standardised a quarter of a century ago, and available in BNF. Redefining the complete language in FPG by hand would be interesting but time consuming and error prone -- not sure that would pay in the end. Maybe writing a BNF2FPG transcompiler would get me there faster... But, without a license I am prohibited from experimenting with it. Even with permission for educational purposes or the like, which I think you have implied, I am not sure that I will be allowed to construct a transcompiler intended for the translation of proprietary source in the end. I am afraid I can't afford the time to investigate the possibilities of FancyPars until legal uncertainties are resolved. Maybe you could consider to make the core of FancyPars Open Source with one of the mainstream licenses, without further restrictions. The parts that you want to keep proprietary I would not publish at all. That way, if somebody else decides to write an analyser, he will not risk infringing the copyright of your closed source, because it is not publicly viewable. Best, Bastiaan.
Re: FancyPars
On Thu, Sep 17, 2015 at 23:40:49 +, Bastiaan Veelo via Digitalmars-d-announce wrote: > On Thursday, 17 September 2015 at 20:32:59 UTC, Stefan Koch wrote: > > Hmm reading this. No license, is best for now. > > Take your time, but without a license anyone cloning or forking > your repo is in fact violating your copyright. It is not what > most people expect on github, and I will have to delete my fork > and local clone... By using public repos, you explicitly allow anyone to view and fork your project. There are no implicit rights of *use* of that clone though. --Ben
