On Monday, 24 June 2024 at 09:52:48 UTC, realhet wrote:
On Sunday, 23 June 2024 at 16:46:05 UTC, monkyyy wrote:
[...]
Good idea, thx!
The two directions of this communication path could be:
1. LDC2 -> External process:
pragma(msg, x) produces specially formatted message to the
stdErr, my b
On Sunday, 23 June 2024 at 16:42:43 UTC, Richard (Rikki) Andrew
Cattermole wrote:
See above why the string imports was designed that way.
I totally forgot the name "string imports". Now I remember,
thanks. That's one data direction of the 2.
On Sunday, 23 June 2024 at 16:46:05 UTC, monkyyy wrote:
On Sunday, 23 June 2024 at 16:33:54 UTC, realhet wrote:
realistically you should just write a build script with two
stages
fun thought experiment time, if you found a programmable
"FUSE"(file system api) database of some sort, mixed `-J`
On Sunday, 23 June 2024 at 16:33:54 UTC, realhet wrote:
Hi,
Is there a way to call an external program from CTFE?
Use case:
Inside a module I want to put some GLSL code.
I also want to generate that GLSL code using CTFE.
And when it's done, it would be nice if I was able to save that
On 24/06/2024 4:33 AM, realhet wrote:
Hi,
Is there a way to call an external program from CTFE?
No. This is on purpose due to "security" and reproducibility concerns.
The nearest thing I've found is the "include file contents" 'macro',
that can be en
Hi,
Is there a way to call an external program from CTFE?
Use case:
Inside a module I want to put some GLSL code.
I also want to generate that GLSL code using CTFE.
And when it's done, it would be nice if I was able to save that
GLSL code into a temp file and call the glsl compiler on it
