On Fri, May 12 2023, Ihor Radchenko <yanta...@posteo.net> wrote: > Leo Butler <leo.but...@umanitoba.ca> writes: > >>> Comments? >> ... >> Replying to myself: it makes more sense to introduce a special-purpose >> header argument for this special purpose, than to use :file with a >> different meaning. Revised patch attached. > > IMHO, it will be more consistent with other backends to use :results file > :file /path/to/executable
No, I don't think this is the way to do it. What happens in this case is: 1. `org-babel-C-execute' creates a named source file, compiles it to the named binary file; 2. then executes that binary file, producing output; 3. that output is inserted into the named binary file, overwriting its contents. I don't see how to accomplish my stated goal of saving the binary file to a named location without introducing a separate header argument (e.g. ":bin-file"). Leo