From: Leo Butler <Leo.Butler@umanitoba.ca>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [RFC/PATCH] naming src/bin files in ob-C.el
Date: Fri, 12 May 2023 20:25:49 +0000 [thread overview]
Message-ID: <874johe1pv.fsf@t14.reltub.ca> (raw)
In-Reply-To: <87jzxdzeoz.fsf@localhost> (Ihor Radchenko's message of "Fri, 12 May 2023 16:39:56 +0000")
On Fri, May 12 2023, Ihor Radchenko <yantar92@posteo.net> wrote:
> Leo Butler <Leo.Butler@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
next prev parent reply other threads:[~2023-05-12 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:05 [RFC/PATCH] naming src/bin files in ob-C.el Leo Butler
2023-05-12 15:41 ` Leo Butler
2023-05-12 16:39 ` Ihor Radchenko
2023-05-12 20:25 ` Leo Butler [this message]
2023-05-13 7:36 ` Ihor Radchenko
2023-05-14 20:19 ` Leo Butler
2023-05-15 11:15 ` Ihor Radchenko
2023-05-15 11:46 ` Leo Butler
2023-05-15 14:02 ` [POLL] ob-C: Should we allow saving compiled src block to specified binary excecutable? (was: [RFC/PATCH] naming src/bin files in ob-C.el) Ihor Radchenko
2023-08-21 12:06 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874johe1pv.fsf@t14.reltub.ca \
--to=leo.butler@umanitoba.ca \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).