On Thu, Jun 27, 2019 at 08:43:00PM +1200, Evan Hanson wrote:
> On 2019-06-27 7:31, megane wrote:
> > Good catch! Didn't intend to change other logic.
> >
> > Fixed version attached.
>
> Thanks, here's a sign-off. I put the variable-mark check back to the way
> it was, to minimise the diff, and
On 2019-06-27 7:31, megane wrote:
> Good catch! Didn't intend to change other logic.
>
> Fixed version attached.
Thanks, here's a sign-off. I put the variable-mark check back to the way
it was, to minimise the diff, and added the new test for Windows.
Evan
>From
Evan Hanson writes:
> Hi megane,
>
> Thanks, this seems like a good fix for now.
>
> On 2019-06-23 17:29, megane wrote:
>> diff --git a/support.scm b/support.scm
>> index f412627d..90635761 100644
>> --- a/support.scm
>> +++ b/support.scm
>> @@ -769,11 +776,11 @@
>> ((assq
Hi megane,
Thanks, this seems like a good fix for now.
On 2019-06-23 17:29, megane wrote:
> diff --git a/support.scm b/support.scm
> index f412627d..90635761 100644
> --- a/support.scm
> +++ b/support.scm
> @@ -769,11 +776,11 @@
> ((assq 'inlinable plist))
>
Greetings,
This is a workaround for the situation described in #1440
I guess in theory the inlining could be supported.
I could get the inlining to work by manually:
1. Adding a "extern" declaration for the foreign stub in the main
program.
2. Linking the main program with the module
