Re: avoid character encoding/escaping in sxml->xml or htmlprag's sxml->html

Re: expression and definition context in Scheme

On 27-08-2022 18:48, Damien Mattei wrote: My ideas is as it is so easy to cheat the compiler I don't think it's cheating or abusive. from seeing the expressio context why does the compiler restrict this? expression and defintion context, i'm not sure they are in scheme standarts, are they rea

Re: expression and definition context in Scheme

On 27-08-2022 21:02, Damien Mattei wrote: I haven't read the RnRS closely, but I doubt that (some-procedure (define foo 0) (define bar 0)) ? i do not understand well the meaning Me neither, that's what I meant. You are proposing to unify expression context and definition context

Re: expression and definition context in Scheme

On 27-08-2022 21:02, Damien Mattei wrote: in fact just allow 'define that act locally ,see my comment below I do not know what semantics you want. Also, even if (begin ...) and (let () ...) where unified, it would be a shame to lose the ability to only have some definitions tempo

Re: expression and definition context in Scheme

On 31-08-2022 09:01, Damien Mattei wrote: I always try to keep compatibility with RnRS and in fact except cond none of when, unless, cond, case, while, and do are in standart RnRS schem 'when', 'unless' and 'do' are actually RnRS, see (rnrs control). 'case' is also RnRS, see (rnrs base). How

Re: [PATCH] Define SO_RCVTIMEO and SO_SNDTIMEO.

On 17-09-2022 10:05, Christopher Baines wrote: + if (ioptname == SO_RCVTIMEO || ioptname == SO_SNDTIMEO) +{ + SCM_ASSERT (scm_is_pair (value), value, SCM_ARG4, FUNC_NAME); How about using SCM_ASSERT_TYPE instead to improve the error message a little? + opt_time.tv_sec = scm

Re: [PATCH] Improve reporting of exception locations

On 20-09-2022 04:00, Andrew Whatson wrote: Most errors were reported as coming from boot-9.scm due to incorrect hard-coded stack-narrowing offsets. This patch fixes the offsets and adds an argument to specify additional frames to skip when calling raise-exception. Do you have some test cases

Re: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

On 20-09-2022 09:23, Andrew Whatson wrote: => (lambda (binding) - (let ((val (frame-local-ref frame (binding-slot binding) - (binding-representation binding + (let* ((slot (binding-slot binding)) +

Re: [PATCH] Improve reporting of exception locations

On 21-09-2022 12:42, Maxime Devos wrote: There recent-ish was a bug report about exception handling (on IRC), it would be a unfortunate if whatever the fix for that turned out to be, causes the reporting to be wrong again -- a few test cases for this patch could prevent that. Correction

Re: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

On 22-09-2022 15:53, Andrew Whatson wrote: - (let ((val (frame-local-ref frame (binding-slot binding) - (binding-representation binding + (let* ((slot (binding-slot binding)) +;; HACK: Avoid out-of-range fro

Re: [PATCH] Add tests for warning locations.

On 24-09-2022 15:46, Andrew Whatson wrote: diff --git a/test-suite/tests/tree-il/unbound-spaces.scm b/test-suite/tests/tree-il/unbound-spaces.scm new file mode 100644 index 0..9de3b9861 --- /dev/null +++ b/test-suite/tests/tree-il/unbound-spaces.scm @@ -0,0 +1 @@ + (foo) diff --git a/

Re: Recursive Macros generating Definitions

On 03-10-2022 13:32, Frank Terbeck wrote: When looking at this, I also saw the following, which might be related if ‘syntax-rules’ is implemented using ‘syntax-case’ It is, IIRC. (I didn't check if this is the case): (define-syntax-rule (foobar n) (define quux n)) ,exp (foobar

Re: Relaxing the copyright assignment policy

On 06-10-2022 22:18, Ludovic Courtès wrote: Hello Guilers! [...] New contributors are encouraged to assign copyright to the FSF by emailing them one of the forms at , especially if they intend to contribute significantly going f

Re: map-par slower than map

On 12-10-2022 19:19, Damien Mattei wrote: Hello, all is in the title, i test on a approximately 3 element list , i got 9s with map and 3min 30s with par-map on exactly the same piece of code!? > [...] > translated from Scheme+ to Scheme: (define unified-minterms-set-1 (map function-unify-m

Re: [DRAFT] Improve reporting of exception locations

On 12-10-2022 08:35, Andrew Whatson wrote: Hello guile-dev! I'm working on a revised patch to improve the reporting of exception locations, after last month's initial flawed attempt. The new patch takes the more radical approach of capturing the stack when an exception is created, AFAICT, i

Re: map-par slower than map

demonstrate the 'map-par slower than map') and to change it to standard-ish Scheme instead of your Scheme+ variant. On Wed, Oct 12, 2022 at 8:45 PM Maxime Devos <mailto:maximede...@telenet.be>> wrote: [rest of copied previous message, without any comments] This is top

Re: Packages depending on (guix build syscalls)

On 20-10-2022 22:05, Ludovic Courtès wrote: Hello Guix! Quite a few packages depend on (guix build syscalls), starting from ‘ant-bootstrap’ (since commit cded3a759356ff66b7df668bcdbdfa0daf96f4c5 in 2018) up to GNOME-related packages such as ‘mutter’ (commit d1c2fe248a7a326189fb7dcae64a59ece96251

Re: Guile VM interpreter in GraalVM Truffle framework

On 23-12-2022 18:06, Arvydas Silanskas wrote: Good day, I have aspirations to run scheme on graalvm's truffle framework. And on superficial research, it seems implementing a Guile VM bytecode interpreter could be easiest path. I just want to inquire, if someone already had similar ideas and i

Re: Guile VM interpreter in GraalVM Truffle framework

On 23-12-2022 21:51, Maxime Devos wrote: [... problems ...] ... you could of course choose to simply _not_ support ephemerons. 'Guile (minus the ephemerons) on top of GraalVM' still sounds interesting even if missing a tiny bit of functionality. Greetin

Re: define-module, #:export and export

On 04-01-2023 16:11, yarl baudig wrote: Hello guile. I don't know if that's a bug. Anyway, I am confused about this so I ask. I came across this problem playing with guix source code. I will share different "tests" each test is a directory with nothing but the files I share. each time the comm

Re: define-module, #:export and export

On 06-01-2023 14:31, yarl baudig wrote: That is also my understanding, confirmed by $ cat lib.scm (define-module (lib)   #:export (test)) (define-syntax test   (lambda (sintax)     (syntax-case sintax ()   ((test id)    (datum->syntax sintax (free-identifier=? #'id #'thing)

Re: [PATCH] Add 'bytevector-slice'.

This looks useful to me, especially once the optimiser recognises 'bytevector-slice'. (In Scheme-GNUnet, I defined a wrapper around bytevectors called 'bytevectors slices' to implement such a thing.) The only thing missing for me, is a procedure 'bytevector-slice/read-only' and 'bytevector-sl

Re: [PATCH] Add 'bytevector-slice'.

On 13-01-2023 12:32, Ludovic Courtès wrote: IIUC, if you use bytevector-slice iteratively, say: (let loop ((bv some-initial-value) (n large-number)) (if (> n 0) (loop (bytevector-slice bv 0 (bytevector-length bv)) (- n 1)) bv)) you will end up with a by

Re: fibers,questions about thread id and mutation of vectors

for (i=start; i<=stop; i++) { /* i is private by default */ scm_init_guile(); scm_call_1( func , scm_from_int(i) ); IIUC, you are calling scm_init_guile once per index, whereas calling it once per thread would suffice. For better performance, I propose doing it once per thread.

Re: [PATCH] Add 'bytevector-slice'.

On 14-01-2023 00:48, Ludovic Courtès wrote: Ah yes, that’s right, I misunderstood the comment. In the example above, where we’re only dealing with slices, we could “skip” the parent (i.e., have each slice’s parent point to the “root” of the hierarchy), but I don’t think we can assume this to b

Re: patch for mmap and friends

On 14-01-2023 01:49, Matt Wette wrote: Please consider this patch for adding mmap(), munmap() and msync()  to libguile/filesys.c.  Included is update for posix.texi and test file mman.test. Once included, feature 'mman should be #t. Matt + if (SCM_UNBNDP (fd)) +c_fd = -1; + else

Re: patch for mmap and friends

On 14-01-2023 23:08, Matt Wette wrote: 2) had to copy/modify dynwind_acquire_port and release_port from ports.c Is it because of the 'static' qualifier? If so, you could use the 'SCM_INTERNAL [...] scm_i_[...]' pattern, e.g. see 'scm_i_is_mutable_bitvector' in libguile/bitvectors.h and li

Re: [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo

On 26-01-2023 19:57, Blake Shaw wrote: don't know how to fix this rn, but... You can escape @ with @@. --- doc/ref/match.texi | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/ref/match.texi b/doc/ref/match.texi index 105150886..c5017e1a5 100644 ---

Re: [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo

On 28-01-2023 10:14, Blake Shaw wrote: Thanks! The new latest edit is still preferred but I'll keep that in mind for the future. I don't follow? The commit message was: [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo don't know how to fix this rn, but... I.e.

Re: [PATCH v1 1/6] docs/match: add pattern matching examples

On 26-01-2023 19:57, Blake Shaw wrote: +A pattern matcher does precisely what the name implies: it matches +some arbitrary pattern, and returns some result accordingly. It doesn't need to return anything -- while functional style is common in Guile, imperative is still possible. It can retu

Re: [PATCH v1 1/6] docs/match: add pattern matching examples

On 26-01-2023 19:57, Blake Shaw wrote: @example -(match lst - (((heads tails ...) ...) - heads)) +(match '(((a b c) e f g) 1 2 3) + (((head ...) tails ...) + `(,@tails ,head))) +@result{} (1 2 3 ((a b c) e f g)) @end example Contrary to the commit message, this isn't an addition of

Re: [PATCH v1 1/6] docs/match: add pattern matching examples

On 29-01-2023 03:40, Blake Shaw wrote: Hi Maxime, Did you watch my talk from Guix days? I read the text in the talk, but mostly skipped the speech. There I detailed that the goal would be to move from what is painfully obvious, gradually building up in chunks and peices. That is what is h

Re: [PATCH v1 1/6] docs/match: add pattern matching examples

On 29-01-2023 04:04, Blake Shaw wrote: On 26-01-2023 19:57, Blake Shaw wrote: >   @example > -(match lst > -  (((heads tails ...) ...) > -   heads)) > +(match '(((a b c) e f g) 1 2 3) > +  (((head ...) tails ...) > +   `(,@tails ,head))) > +@result

Re: [PATCH v1 1/6] docs/match: add pattern matching examples + CoC

do know that it was enough for me to become allergic to Guile/Guix community until I started hanging out on Mastodon and discovered many guix have retreated there. Now let's get into the specifics of the current patch review where I'll show why I think your efforts aren't in earne

Re: [PATCH v1 1/6] docs/match: add pattern matching examples

On 30-01-2023 20:56, Aleix Conchillo Flaqué wrote: [...] Maxime found the time to review a quite big PR and added a bunch of useful comments. Reviewing that PR took a lot of effort and I just felt better after fixing all the comments made. I was even surprised he (I'm assuming this pronoun) did

Re: [PATCH v3] docs/match: pattern matcher example makeover

On 01-02-2023 14:09, Blake Shaw wrote: [...] - style: clean-up newlines -- It appears that while the PDF needs additional newlines to be presentable, these appear to have a negative effect on the presentation of the texinfo doc. I don't know how to fix this, but from looking at the PDF, it ap

Re: [PATCH] add language/wisp to Guile?

Why add Wisp? For Wisp: it is then available directly wherever Guile is available. This will make it much easier for people to follow tutorials. I'm not convinced of this argument, because package managers exist, but ... For Guile: - Wisp has proven to be good at enabling people to

Re: [PATCH] add language/wisp to Guile?

On 04-02-2023 16:46, Dr. Arne Babenhauserheide wrote: [...] So I’d like to ask: can we merge Wisp as supported language into Guile? From some conversations elsewhere, I got the impression that (use-modules (foo)) will search for foo.scm and not in foo.w. I think you'll need to tweak the

Re: [PATCH] add language/wisp to Guile?

On 04-02-2023 22:35, Dr. Arne Babenhauserheide wrote: Maxime Devos writes: This needs an addition to the extensions via guile -x .w — I wrote that in the documentation. I didn’t want to do that unconditionally, because detecting a wisp file as scheme import would cause errors. If done

Re: [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized

> [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized On 06-02-2023 19:34, Jose E. Marchesi wrote: Hello Guile hackers. We are in the process of integrating GNU poke[1] in GDB by mean of libpoke. Problem is, libpoke uses the Boehm GC, as guile does. We are working on switching to

[PATCH] Print backtraces for syntax errors too.

For complicated macros, especially macros that are used correctly but have a bug in their implementation somewhere and use 'syntax-case' or 'syntax-rules' multiple times, it can be very convenient to know _which_ syntax-case or syntax-rules raised the syntax-error. E.g., I'm currently debugging so

Re: [PATCH] add language/wisp to Guile?

> [...] That would be nice, but would require doing changes in a critical core part of Guile. It would change this addition from a risk-free added feature to a risky core change. I maintain that a new language shouldn't be merged until the Scheme-specific load path stuff is fixed/extended to w

Re: [PATCH] add language/wisp to Guile?

[...] Which begs an important question: How would you like to be attributed? I plan to also merge this back to the wisp repo and I’d like to attribute you there, too. You could add a ";; Copyright © 2023 Maxime Devos " line next to yours in the file that contains the read-one-w

Re: [PATCH] add language/wisp to Guile?

On 16-02-2023 09:03, Dr. Arne Babenhauserheide wrote: Maxime Devos writes: + ;; allow using "# foo" as #(foo). + (read-hash-extend #\# (λ (chr port) #\#)) That's a rather Wisp-specific extension, but it appears you are extending things globally. Ins

Re: [PATCH] add language/wisp to Guile?

On 16-02-2023 22:38, Dr. Arne Babenhauserheide wrote: Matt Wette writes: You may be interested in the load-lang patch I generated a few years ago to allow file-extension based loading, in addition to '#lang elisp" type hooks. https://github.com/mwette/guile-contrib/blob/main/patch/3.0.8/lo

Re: [PATCH] add language/wisp to Guile?

On 18-02-2023 04:50, Philip McGrath wrote: I haven't read the patch or this thread closely, I'll assume you have read it non-closely. but R6RS has an answer to any concerns about compatibility with `#lang`. At the beginning of Chapter 4, "Lexical and Datum Syntax" (

Re: [RFC,PATCH] Do not GC_INIT the Boehm GC if already initialized

On 20-02-2023 11:06, Ludovic Courtès wrote: [...] The “Multiple invocations” bit isn’t in libgc 8.0.4. Which version are you looking at? Commit 151b49a5302eea89ffd9efd9cdb82b75ac4f5d35 (include/gc/gc.h). Looking at the changelog, that part is there since at least 8.0.6: [...] * Refine GC_IN

Re: [PATCH] add language/wisp to Guile?

In Racket, in the initial configuration of the reader when reading a file, "`#!` is an alias for `#lang` followed by a space when `#!` is followed by alphanumeric ASCII, `+`, `-`, or `_`." (See .) [...] > (Guile does

Re: [PATCH] add language/wisp to Guile?

On 23-02-2023 09:51, Dr. Arne Babenhauserheide wrote: Thinking a bit more about it, it should be possible to special-case Guile's interpretation of "#!" such that "#!r6rs" doesn't require a closing "!#". (Technically backwards-incompatible, but I don't think people are writing #!r6rs ...!# in th

Re: [PATCH] add language/wisp to Guile?

On 23-02-2023 19:04, Maxime Devos wrote: Still doesn't really address the problem though, as Scheme scripts (or scripts in another language) may need to start with a shebang and "#!lang" or "#lang" is not a valid comment in all languages.  (E.g., I don't think it

Re: [PATCH] add language/wisp to Guile?

On 23-02-2023 19:04, Maxime Devos wrote: (*) Java actually allows "#!", but only in 'Shebang' files (see: https://openjdk.org/jeps/330#Shebang_files).  It remains invalid to put a '#!java' line in files with a class definition that is supposed to be found by Jav

Re: [PATCH] add language/wisp to Guile?

On 23-02-2023 19:04, Maxime Devos wrote: (*) Java actually allows "#!", but only in 'Shebang' files (see: https://openjdk.org/jeps/330#Shebang_files).  It remains invalid to put a '#!java' line in files with a class definition that is supposed to be found by Jav

Re: [PATCH] add language/wisp to Guile?

On 23-02-2023 12:36, Ludovic Courtès wrote: Hi! Sorry for the late reply. FWIW, I think it might be best to keep Wisp as a separate package: that allows it to evolve independently of Guile (and possibly more quickly :-)), and it might simplify maintenance in some way. To my understanding, W

Re: [PATCH] Print backtraces for syntax errors too.

On 23-02-2023 12:38, Ludovic Courtès wrote: Do you have a simple reproducer and a before/after comparison showing what Guile prints? Simpler reproducer: (define-syntax syntax-stuff-twice (lambda (s) (define (f x) (syntax-case x () (#:this #''this) (#:that #''that)))

Re: [PATCH] Print backtraces for syntax errors too.

On 23-02-2023 12:38, Ludovic Courtès wrote: Do you have a simple reproducer and a before/after comparison showing what Guile prints? (Please ignore my previous e-mail, the reproducer was incorrect. I'll try making another one.) OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public ke

Re: [PATCH] Print backtraces for syntax errors too.

On 23-02-2023 12:38, Ludovic Courtès wrote: Hi, Maxime Devos skribis: For complicated macros, especially macros that are used correctly but have a bug in their implementation somewhere and use 'syntax-case' or 'syntax-rules' multiple times, it can be very convenient to

Re: [PATCH] Print backtraces for syntax errors too.

On 24-02-2023 16:48, Ludovic Courtès wrote: Maxime Devos skribis: ;; Before: ;; unknown file:#f:#f: syntax-stuff-twice: bad in subform # of # ;; After: ;; [the same thing] ;; ;; Looks like another patch is needed ... What backtrace are you trying to get? Getting a backtrace

Re: [PATCH] add language/wisp to Guile?

On 24-02-2023 16:45, Ludovic Courtès wrote: Adding #lang support in Guile would be nice. As discussed on IRC, it can be experimented with in a WIP branch. Have you seen my messages on how the "#lang" construct is problematic for some languages, and how alternatives like "[comment delimiter] -

Re: [PATCH] add language/wisp to Guile?

On 25-02-2023 00:48, Maxime Devos wrote: (**) For compatibility with Racket, it's not like we couldn't implement both "#lang" and "-*- stuff: language -*-". TBC, I mean ‘only support #lang' for values of 'lang' that Racket supports’, or altern

Re: [PATCH] add language/wisp to Guile?

On 25-02-2023 01:15, Matt Wette wrote: On 2/24/23 3:51 PM, Maxime Devos wrote: On 25-02-2023 00:48, Maxime Devos wrote: (**) For compatibility with Racket, it's not like we couldn't implement both "#lang" and "-*- stuff: language -*-". TBC, I mean ‘only supp

Re: [PATCH] add language/wisp to Guile?

Op 26-02-2023 om 08:45 schreef Philip McGrath: Hi, On Sat, Feb 18, 2023, at 10:58 AM, Maxime Devos wrote: On 18-02-2023 04:50, Philip McGrath wrote: I haven't read the patch or this thread closely, I'll assume you have read it non-closely. but R6RS has an answer to any conc

Re: Functional datatypes in Guile

Op 27-02-2023 om 14:17 schreef Jessica Tallon: Hello, I've been thinking how it'd be nice to have available in Guile a number of purely functional datatypes, these being hashmaps, vectors, and sets. I've been wondering what folks have been using for these with the idea that we could bring them

Re: Clojure support

Op 14-05-2023 om 00:10 schreef Rob Browning: Regarding hash-maps and hash-sets, I initially used pfds, but after having trouble with bugs, I switched to fash: https://codeberg.org/lokke/lokke/commits/branch/main/search?q=pfds Guix has included a fix tor the hamts bug: #:phases (mo

<    1   2   3   4   >