Re: Source code output

2013-07-17 Thread John Colvin
On Wednesday, 17 July 2013 at 05:29:26 UTC, H. S. Teoh wrote: On Wed, Jul 17, 2013 at 05:27:34AM +0200, JS wrote: With heavy ctfe code generation usage is it possible to have the d compiler output the source code after all mixin templates have been "used"? This way it is easier to visually chec

Re: Source code output

2013-07-17 Thread Jacob Carlborg
On 2013-07-17 16:13, Ary Borenszweig wrote: Since Descent used a port of the D compiler to Java, I think the same can be done by tweaking dmd. You have the generated AST after semantic analysis and you can easily output that. But of course you need to be able to convert the AST to string with co

Re: Source code output

2013-07-17 Thread Ary Borenszweig
On 7/17/13 4:33 AM, Jacob Carlborg wrote: On 2013-07-17 05:27, JS wrote: With heavy ctfe code generation usage is it possible to have the d compiler output the source code after all mixin templates have been "used"? This way it is easier to visually check for errors in the generated code. I ima

Re: Source code output

2013-07-17 Thread Jacob Carlborg
On 2013-07-17 05:27, JS wrote: With heavy ctfe code generation usage is it possible to have the d compiler output the source code after all mixin templates have been "used"? This way it is easier to visually check for errors in the generated code. I imagine one could use pragma in a "special way

Re: Source code output

2013-07-17 Thread dennis luehring
Am 17.07.2013 09:33, schrieb Jacob Carlborg: On 2013-07-17 05:27, JS wrote: With heavy ctfe code generation usage is it possible to have the d compiler output the source code after all mixin templates have been "used"? This way it is easier to visually check for errors in the generated code. I

Re: Source code output

2013-07-16 Thread JS
On Wednesday, 17 July 2013 at 05:29:26 UTC, H. S. Teoh wrote: On Wed, Jul 17, 2013 at 05:27:34AM +0200, JS wrote: With heavy ctfe code generation usage is it possible to have the d compiler output the source code after all mixin templates have been "used"? This way it is easier to visually chec

Re: Source code output

2013-07-16 Thread H. S. Teoh
On Wed, Jul 17, 2013 at 05:27:34AM +0200, JS wrote: > With heavy ctfe code generation usage is it possible to have the d > compiler output the source code after all mixin templates have been > "used"? This way it is easier to visually check for errors in the > generated code. > > I imagine one cou

Source code output

2013-07-16 Thread JS
With heavy ctfe code generation usage is it possible to have the d compiler output the source code after all mixin templates have been "used"? This way it is easier to visually check for errors in the generated code. I imagine one could use pragma in a "special way" to do this but I was hopin