bug#43025: re-export-public-interface fails on Guile 3

Hi Dale. Am Montag, den 24.08.2020, 12:11 -0400 schrieb Dale Smith: > This is actually reported by daviid on IRC. > > This definition of re-export-public-interface works fine on Guile > 2.x, > fails with Guile 3: > (hope this makes it through the mails cleanly) > ;;; > ;;; re-export-public-inter

bug#43025: re-export-public-interface fails on Guile 3

Am Mittwoch, den 26.08.2020, 12:51 -0400 schrieb Dale Smith: > On 8/24/20, Leo Prikler wrote: > > My solution for this problem would be to build on some of the > > module > > "intrinsics", which sadly are not all that well documented. > > > > (def

bug#44050: [PATCH] doc-snarf: Add support for (ice-9 optargs) define*s.

* module/scripts/doc-snarf.scm (supported-languages)[scheme]: Limit signature start to define and define*. (peek-sexp): New variable. (find-std-int-doc): Implement in terms of peek-sexp. (parse-entry, make-prototype, get-symbol): Use full function definition instead of def-line. (snarf): Adjust acc

bug#44186: Recursive mkdir

Hello, divoplade, > So, after a bit of bikeshedding on #guile, it turns out that the > controversy moved to the second commit. Not quite, the second commit just needlessly complicates a patch, that should not be that complicated in the first place. When posting a patch to the mailing list, you sho

bug#44186: Recursive mkdir

turning #t on error won't actually fix them. > As for the first commit: > > Le lundi 26 octobre 2020 à 22:05 +0100, Leo Prikler a écrit : > > I'd prefer it if you didn't credit me for messing up your code. ;) > > The reason my version works, is because (ice-9 files

bug#45131: [PATCH] Compile directly to target language if no joint is found.

This enables the compilation from "manually" written Tree-IL to bytecode. See also . * system/base/compile.scm (read-and-compile)[(joint #f)]: Join exps using the default joiner for to. : Compute compiler for to. * test-suite/test/compiler.test ("read-and-compile tree-

bug#47875: Elisp reader doesn't handle keywords

Hi Guilers, Using Guile 3.0.5, the elisp reader does not seem to support keywords written in Elisp's preferred prefix-style notation (:keyword). scheme@(guile-user)> ,L elisp Happy hacking with Emacs Lisp! To switch back, type `,L scheme'. elisp@(guile-user)> :keyword ice-9/boot-9.scm:1669:16: I

bug#47875: Elisp reader doesn't handle keywords

Am Samstag, den 05.06.2021, 18:51 +0300 schrieb Ivan Sokolov: > In Scheme keywords and symbols are separate entities, but in Elisp > keywords are just self-quoted symbols. I think your solution will > cause problems with Elisp algorithms that expect keywords to be > symbolp. You could define Elisp

bug#48425: Should #nil be equal? to '()?

Hi Taylan, after a lengthy discussion in IRC, you invited me to reply to this bug report, so that's what I'm doing. I will make short references to that discussion, but I won't rehash all of it. Anyone who is interested in reading it in all detail, should inspect the public logs: http://logs.g