> On Jul 28, 2017, at 11:34 AM, Stefan Israelsson Tampe
> wrote:
>
> Hi all. We have goops, but I wondered how a functional object system can look
> like and after some thought I modeled together functional and python together
> with scheme. you can find the result at
>
> http://www.c-lambda
> On Jul 15, 2017, at 6:15 AM, Matt Wette wrote:
>
>
>> On Jul 14, 2017, at 9:35 PM, Matt Wette wrote:
>>
>>
>>> On Jul 14, 2017, at 5:44 PM, Amirouche Boubekki
>>> wrote:
>>>
>>> On 2017-07-15 01:17, Matt Wette wrote:
I tried git2 but those headers are too
broken.
>>>
>>> What
Matt Wette writes:
> NYACC version 0.80.4 is released
>
> This is a bug-fix release, to fix several bugs discovered by janneke. Thanks
> Jan.
> 1) C parser not parsing “0ULL” as numeric; fixed.
> 2) #undef FOO not working; fixed;
> 3) struct foo { …} => (struct-def (ident (“foo”))… ; fixed: =>
Another possibility beside docstrings would be to add it as a property
to the function. I'm not sure if this is a documented feature, but if
the first form in a function is a literal vector rather than a string
(or in addition to a string, I've just found out!), it will be
interpreted as a sequence
> On Aug 1, 2017, at 1:53 PM, Jan Nieuwenhuizen wrote:
>
> Matt Wette writes:
>
>> NYACC version 0.80.4 is released
>>
>> This is a bug-fix release, to fix several bugs discovered by janneke.
>> Thanks Jan.
>> 1) C parser not parsing “0ULL” as numeric; fixed.
>> 2) #undef FOO not working; f
Matt Wette writes:
> Thanks for the reports. I am happy to see the severity in bugs reducing.
Yes!
> For the FFI-helper I need to parse the rat’s nest under /usr/include
> so I am catching more.
Hah :-)
> I am not sure what you are getting at here. If I have
> char *s = “foo\0bar”;
> t
