> On 29 Jun 2018, at 17:35, Chris Vine wrote:
>
> On Fri, 29 Jun 2018 12:34:07 +0200
> Hans Åberg wrote:
>>> If, say, uint8_t is available in stdint.h for C, it
>>> will be available for C++. §21.4.1/2 of C++17 makes this even more
>>> explicit: "The [cstdint] header defines all types and
Greetings Andy!
Andy Wingo wrote:
> Hi,
>
> Just wanted to give an update on Guile 3 developments. Last note was
> here:
>
> https://lists.gnu.org/archive/html/guile-devel/2018-04/msg4.html
>
> The news is that the VM has been completely converted over to call out
> to the Guile
On Sat 23 Jun 2018 22:12, Andy Wingo writes:
> Is there anyone who compiles Guile with a compiler that does not support
> C99? If so, please give platform and compiler.
>
> I think my questions are limited to, in decreasing order of importance:
>
> * Is there any system that we target that
Hi,
Just wanted to give an update on Guile 3 developments. Last note was
here:
https://lists.gnu.org/archive/html/guile-devel/2018-04/msg4.html
The news is that the VM has been completely converted over to call out
to the Guile runtime through an "intrinsics" vtable. For some
> On 29 Jun 2018, at 09:39, Andy Wingo wrote:
>
> It would seem that the first four
> features of C99 are OK for all platforms that we target, with the
> following caveats:
>
> * We should avoid using C++ keywords (e.g. throw) in Guile API files.
>
> * We might want to avoid mixed decls and
On Fri, 29 Jun 2018 12:34:07 +0200
Hans Åberg wrote:
> > On 29 Jun 2018, at 12:10, Chris Vine wrote:
> >
> >> For C++, these are only optional, cf. [1], as they require no padding. So
> >> an alternative is to typedef the obligatory int_fast<2^k>_t types, perhaps
> >> leaving the API
> On 29 Jun 2018, at 12:10, Chris Vine wrote:
>
>> For C++, these are only optional, cf. [1], as they require no padding. So an
>> alternative is to typedef the obligatory int_fast<2^k>_t types, perhaps
>> leaving the API unchanged.
>>
>> 1. https://en.cppreference.com/w/cpp/types/integer
>
On Fri, 29 Jun 2018 10:39:33 +0200
Hans Åberg wrote:
> > On 29 Jun 2018, at 09:39, Andy Wingo wrote:
> >
> > It would seem that the first four
> > features of C99 are OK for all platforms that we target, with the
> > following caveats:
> >
> > * We should avoid using C++ keywords (e.g. throw)
Hi,
I'm encountering a few crashes with Fibers that happen when I call
CALL-WITH-NEW-THREAD in a Fiber. TEST4 crashes every time. TEST5 never
outputs, but it doesn't crash every time.
TEST1 is exactly like TEST5 except that I replace CALL-WITH-NEW-THREAD
with SPAWN-FIBER.
Is it a mistake from
