On 7/21/11 2:14 AM, Andrej Mitrovic wrote:
Ok, but the other CTFE issues are still there:
D:\dev\projects\qtd\examples\desktop\systray>dmd -unittest
-version=QtdUnittest -I..\..\..\build_dir\build -I..\..\..\d2
..\..\..\build_dir\build\lib\qtdcore.lib
..\..\..\build_dir\build\lib\qtdgui.lib qrc_systray.d window.d main.d
-ofsystray
..\..\..\d2\qtd\MOC.d(271): Error: gen.output ~= format_ctfe("\x0a //
content:\x0a") cannot be evaluated
at compile time
..\..\..\d2\qtd\MOC.d(272): Error: cannot evaluate format_ctfe("
${}, // revision\x0a",2) at compile time
..\..\..\d2\qtd\MOC.d(484): Error: cannot evaluate generateCode(gen)
at compile time
..\..\..\d2\qtd\MOC.d(513): Error: cannot evaluate generateMetaInfo()
at compile time
..\..\..\d2\qtd\MOC.d(513): Error: argument to mixin must be a string,
not (generateMetaInfo())
Well, seems like I never built one of my applications since the CTFE
overhaul was merged into master… ;) It would be great if you could have
a short look at what actually got broken. qtd.MOC is hand-written, so
tracking that CTFE regression [1] down without going insane should be
possible. By the way, pretty much all of my QtD code is D2.
If you don't have time for it, I will definitely have a look at it at
some point in the future, but after my Thrift project, updating LDC 2 is
currently on top of my todo list.
Thanks,
David
[1] From a DMD development perspective, it might be that this isn't a
regressions because the feature might not have worked correctly before,
but it certainly did the job. If I were to make a wild guess, I'd try
manually setting gen.output to [] if it should be null at that point,
because I had a similar problem after the overhaul with strings, but as
this is supposed to be fixed, it's probably something else.
