On Thursday, 24 January 2013 at 13:12:31 UTC, Bruno Medeiros
wrote:
On 21/01/2013 21:14, alex wrote:
Hi everyone,
No, the entire formatting engine is NOT finished yet. :P
Anyway I've created a good compromise solution between
releasing
stuff early and having a fairly nice formatting result:
I just let the indenting engine calculate the indents of all
lines of the code - and fix all the incorrect indents
afterwards.
It works quite fast & reliable(?) - I hope it won't throw very
often + you don't have to worry about resetting your code to an
earlier state via [Ctrl+Shift][Z]
Indenting only parts of the code is possible either! - So you
don't have to worry about your entire code getting messed up
probably ;)
More info @ http://mono-d.alexanderbothe.com
Issues: https://github.com/aBothe/Mono-D/issues
That's a lot of continuing nice work coming out from there,
impressive!
BTW, something I've been meaning to ask. I see that in Mono-D
you've developed a hand-written D parser. How long did it take
you to write that? Did you test it extensively or not so much?
I'm embarking on that same task in Java, for DDT, and wondering
how long it will take to build a quality parser. So far, it
doesn't seem writing the actual parser will take that long, but
writing extensive tests for it is seeming exceedingly
complicated (or just lengthy and time-consuming). I'm usually a
big proponent of TDD, but when writing a lot of tests starts to
take a lot of time compared to the code being tested (in this
case, maybe 1.5 times the effort/time of the code being
tested), I'm not so certain it's the right call to spend so
much time writing tests...
Are you making use of JavaCC or ANTLR?
