Right, engine-interface.scm is one of several files of helper code to make it
easier or more idiomatic to write scheme code using the engine. They're not in
the path if one uses the engine API from Scheme. Contrast that with using an
options dialog from C: That goes through the Scheme options co
I've managed to enter some guile code from the register: "Transaction >
Copy Transaction" will copy the current transaction into an scm object via
functions in engine-interface.scm, called from split-register.c, and I
presume this scm object is read back to paste later on. Ditto Transaction >
Dupli
Op zaterdag 27 april 2019 16:05:42 CEST schreef John Ralls:
> > On Apr 26, 2019, at 10:55 PM, Geert Janssens
> > wrote:>
> > Op zaterdag 27 april 2019 01:01:38 CEST schreef John Ralls:
> >> What Geert meant is that our current engine code *isn't* particularly
> >> portable, though I think that si
> On Apr 26, 2019, at 10:55 PM, Geert Janssens
> wrote:
>
> Op zaterdag 27 april 2019 01:01:38 CEST schreef John Ralls:
>> What Geert meant is that our current engine code *isn't* particularly
>> portable, though I think that since it compiles OK on MacOS it shouldn't
>> have too much trouble
> On Apr 26, 2019, at 8:16 PM, Stephen M. Butler wrote:
>
> On 4/26/19 4:04 PM, John Ralls wrote:
>>
>>> On Apr 26, 2019, at 10:04 AM, Stephen M. Butler wrote:
>>>
>>> Based on the following, have I run into a problem with googletest on
>>> Disco? Additional Guidance sure appreciated.
>>>
