CTFE output is kind of weired

[H. S. Teoh via Digitalmars-d-learn]

On Sun, Jul 09, 2017 at 06:48:30AM +0000, Stefan Koch via Digitalmars-d-learn wrote:
> On Sunday, 9 July 2017 at 04:03:09 UTC, H. S. Teoh wrote:
[...]
> > Stefan Koch allegedly will add a ctfeWriteln to his new CTFE engine
> > that should alleviate this limitation.
> > 
> > 
> > T
> 
> In fact ctfeWriteln harder to do for newCTFE then it is in the old
> interpreter.
[...]

Oh? Why is that?  Isn't it just a matter of adding a new opcode for
outputting a string?  Or calling an intrinsic function that the
interpreter recognizes as ctfeWriteln?


T

-- 
ASCII stupid question, getty stupid ANSI.