emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Leo Butler <Leo.Butler@umanitoba.ca>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [RFC/PATCH] naming src/bin files in ob-C.el
Date: Mon, 15 May 2023 11:15:04 +0000	[thread overview]
Message-ID: <87pm71hmmf.fsf@localhost> (raw)
In-Reply-To: <878rdqd5tc.fsf@t14.reltub.ca>

Leo Butler <Leo.Butler@umanitoba.ca> writes:

> Ok, stopping after 1 seems reasonable when the code block is meant to
> produce just the executable. But, your suggestion would mean that the
> code block can *only* produce an executable file. Maybe that is ok, but
> since the current semantics allow something like
> #+begin_src C++ :includes <iostream> <fstream> :results file :file ./results.csv
>   using namespace std;
>   for(int i=0; i<10; i++){ cout << i << "," << i*i << endl; }
> #+end_src
> so I am not sure that we should break that.

Fair point.

> On the other hand, I don't see any sense in producing a link to the
> binary file. Org can't do anything with that link, so the user would
> need to write something like ":results file :file /path/to :wrap
> comment". That is why I would prefer something like a :bin-file header.

I am not sure how I feel about such side effects of evaluation.
Is there any other babel backend that is doing something similar?

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  reply	other threads:[~2023-05-15 11:12 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
2023-05-13  7:36       ` Ihor Radchenko
2023-05-14 20:19         ` Leo Butler
2023-05-15 11:15           ` Ihor Radchenko [this message]
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:

  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=87pm71hmmf.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=Leo.Butler@umanitoba.ca \
    --cc=emacs-orgmode@gnu.org \


* 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


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).