Re: GNU Guile 2.1.7 released (beta)

On Fri 24 Feb 2017 18:46, Arne Babenhauserheide writes: > The main strategical question I see for that is: Does anything make it > harder to complete or improve the lilypond transition to Guile 2? > > Is there something which would need to be done before 2.2 which could > make it easier for lilyp

Re: [PATCH] Explain why no native accessors for `s8' and `u8' exist

Happy to apply; can you fix up the changelog? Just see any recent commit to this file for the format. Thanks :) Andy On Thu 23 Feb 2017 20:48, "Diogo F. S. Ramos" writes: > Instead of saying it is obvious, explain why no native endianness > accessors exist for the `s8' and `u8' variants. > --

Re: Guile security vulnerability w/ listening on localhost + port (with fix)

Hi! On Fri 14 Oct 2016 23:55, Lizzie Dixon <_...@lizzie.io> writes: > I know it's a late kudo but still -- great investigation and writeup, thank you for digging in to this one :) Andy

Possible bug closures

This one seems fixed. Reporter suggests it can be closed: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25267 This seems no longer relevant; I believe it's a candidate for closure: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25700

[PATCH] Explain why no native accessors for `s8' and `u8' exist

* doc/ref/api-data.texi: Instead of saying it is obvious, explain why no native endianness accessors exist for the `s8' and `u8' variants. --- doc/ref/api-data.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi index 1b3170

Guile-2.2 - goops setters should be inherited, no matter what :)

Hello Andy, > * GOOPS: are there incompatible changes that we think are bad? >Subthread :) In my opinion, this would be the right time to make changes so that goops follows the clos protocol (for the (quite large) subset it implements), I don't pretend I have ident

Guile-2.2 - goops slot redefinition at subclass level

Hello Andy, > * GOOPS: are there incompatible changes that we think are bad? >Subthread :) 2- slot redefinition at subclass level See bug#20423 for a full description, here is the summary of what I think we should do: When there are superclasses, a subclass can specify a