Conrad Vermeulen
Conrad Vermeulen
Maybe easier to use the CompilerVersion in the conditional directive: {$IF defined(DCC) and (CompilerVersion >= 2.1)} {$DEFINE VER210ORGREATER} {$IFEND} {$IF defined(DCC) and (CompilerVersion >= 2.3)} {$DEFINE VER230ORGREATER} {$IFEND} {$IF defined(FPC)}...
Where was the comma?
Shall I close this?
I'll double check the gist to see if I can reproduce
It seemed to work fine for me. I just had to change: cTmplStr = '{{ FuncB('/file1.txt') }}'; to cTmplStr = '{{ FuncB("/file1.txt") }}'; but I think that may have been...
Thanks. I think this may be worth reviewing to support with more flexibility... I think there may be an option that doesn't impose too much of an overhead to support...
``` var lctx:=template.context; lctx.addfunctions(TTmplFunctions); ltpl := template.parse(lctx, '....'); writeln(Template.Eval(lCtx, lTpl, ldata)); ``` does the above make sense?
Ah, sorry, I didn't appreciate the issue you highlighted... All helpers are expected to be functions... so they should return something. maybe change SetThemeData to something like: class function SetThemeData(const...
I think it depends on how you are outputting stuff. Ideally, there should not be any issue. If you are following the model of passing data into the template rather...
actually, I was reviewing what you said again about nested templates... The template engine uses 'stack frames' for storing variables. I can't recall offhand, but it may be that when...