Ihor Radchenko writes:
> I feel slightly reluctant about adding side effects to babel evaluation.
> Not too reluctant though.
>
> I'd like to hear from other ob-C users, so I changed this thread into a poll.
No replies.
Closed.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more
Leo Butler writes:
>> I am not sure how I feel about such side effects of evaluation.
>> Is there any other babel backend that is doing something similar?
>
> ob-java.el deals with it by using a :dir header; if non-nil, the
> compiled files are placed in that directory instead of
>
On Mon, May 15 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> 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
Leo Butler 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
>
>
On Sat, May 13 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>>> 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'
Leo Butler writes:
>> 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
On Fri, May 12 2023, Ihor Radchenko wrote:
> Leo Butler 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
Leo Butler 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
On Fri, May 12 2023, Leo Butler wrote:
> Hello,
>
> I am using ob-C.el to work with a c++ library (capd::dynsys). The
> current behaviour creates a temporary src and bin file in
> `org-babel-temporary-directory'. There is currently no option to have
> these files named and put somewhere else.
>
Hello,
I am using ob-C.el to work with a c++ library (capd::dynsys). The
current behaviour creates a temporary src and bin file in
`org-babel-temporary-directory'. There is currently no option to have
these files named and put somewhere else.
This behaviour is not quite right, in my opinion. I
10 matches
Mail list logo
