Re: Hygienic rewrite of (ice-9 expect)

I think this would gather more replies if: 1. It is sent as a patch that can be applied to the Guile source tree. (You wrote: > If the community likes this implementation, I would be happy to > apply/rebase my changes onto the official repo, and then we can go > from there! but to determine w

Re: Hygienic rewrite of (ice-9 expect)

>p 29-05-2023 om 03:40 schreef Daniel Dinnyes: Thanks for the reply. On Sun, 28 May 2023 at 14:39, Maxime Devos <mailto:maximede...@telenet.be>> wrote: I think this would gather more replies if:   1. It is sent as a patch that can be applied to the Guile source tre

Re: Guile 64-bit Windows support, redux

Op 06-06-2023 om 22:50 schreef Mike Gran: Hello Guile, There have been a few times where I made Guile work on MinGW -- usually the 32-bit, unthreaded variety -- because I wanted it for my own entertainment.  Often around the time of the Lisp Game Jam. The Game Jam just happened, so I was pokin

Re: Guile 64-bit Windows support, redux

Op 08-06-2023 om 22:46 schreef Mike Gran: But when I get back to it, I'll try to be more precise 1. long or long long - an integer that is "big" in some general sense 2. int64_t - an integer that needs to be 64-bit because may hold a large integer 3. intptr_t - an integer that holds a pointer

Re: [PATCH] add SRFI-119 / language/wisp to Guile? (new patch, squashed)

ce helpful error messages (and internationalized, too). Agreed. > [...] Can you make it LGPLv3+? It’s a small file anyway. Only if David A. Wheeler, Alan Manuel K. Gloria and Maxime Devos agrees. Otherwise, you still need to include the license text: > [...] +;;; The above copyright notice

Re: Hygienic rewrite of (ice-9 expect)

Will look later ... have been busy. I expect to have time after ~2 weeks. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: The message chain with an happy ending

I don't see the relation with Guile. What's guile-devel@gnu.org doing in the To:? Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: The message chain with an happy ending

. (*) To list an example: <https://forums.sufficientvelocity.com/threads/welcome-to-science-technology.41297/>. Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

What's to be considered on-topic for Guile mailing lists? (Re: The message chain with an happy ending)

happened yet -- it's still named guile-devel (i.e., __development__) -- it needs a name change, or some documentation in the manual. Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: The message chain with an happy ending

(In future responses, let's trim the CC:) OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: Hygienic rewrite of (ice-9 expect)

haven't directly compared the (ice-9 expect) with the (ice-9 expect) yet, but it should now be simple to verify (and anyway, there are tests). Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH] Add statvfs bindings.

ef', or by the method used in libguile/goops.c. I haven't really looked at the documentation or implementation. Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH] Allow specifying the socket style for open-socket-for-uri.

Op 20-07-2023 om 16:08 schreef Christopher Baines: Since this allows specifying additional behaviours for the socket through using SOCK_CLOEXEC and/or SOCK_NONBLOCK (when bitwise or'ed with SOCK_STREAM). Note that Guile/guile-gnutls currently doesn't support performing the TLS handshake on a n

Re: [PATCH] web: Support reading chunked request bodies.

thing). Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH v2] Add atomic-box-update! function to (ice-9 atomic)

d in multiprocessor systems—where many threads constantly update some particular shared variable—if threads that see their CAS fail use exponential backoff—in other words, wait a little before retrying the CAS.[4] Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH] doc: Extend documentation for (ice-9 match)

Op 06-09-2023 om 16:06 schreef Tomas Volf: > Extend the documentation for (ice-9 match) module with explanation of > some of the patterns and also provide more examples for them. That > should make it more useful for people trying to use the module for the > first time just based on the documen

Re: Replacing Guile test-suite with SRFI-64?

Op 23-09-2023 om 17:13 schreef Mike Gran: Hi, Would a rewrite of the Guile tests using SRFI-64 be a welcome idea? IMO the advantages of doing so are: ... Opinions? IMHO, I think Guile should not depend too heavily on Guile for testing itself. It is bad bootstrapping practice. Whether

Re: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity

le for loading .go/.scm can be adjusted to add a prefix turning it in an absolute file name. > One wrong way to find out the absolute path would be to go through > %load-path, but the semantics of that would break under mutation. > Best regards, Can you elaborate? Maxime Devos.

Re: Replacing Guile test-suite with SRFI-64?

it turns out to be justification for updating the test suite, then how would that be a bad thing? After all, it would be justified. (Also, which test suite are you talking about -- the test suite of SRFI-64, or Guile's test suite in its entirety?) Best regards, Maxime Devos. OpenPGP_0

Re: Feature request: make Guile compiler always write absolute paths in .go files for Geiser compatiblity

Op 25-09-2023 om 11:36 schreef Vili Aapro: On Mon, 25 Sep 2023 11:26:31 +0200 Maxime Devos wrote: Sounds like a very bad idea. The absolute file name would be somewhere in the build directory, which very likely doesn't exist anymore on a typical installation. Yes, you are right

Re: [PATCH v2 4/4] load: Display modules depth in output when using %load-verbosely.

ync-mark that prints output, when possible I recommend that the interrupt procedure doesn't assume the port isn't temporarily changed.) (*) Roughly similar to C signal handlers. (I now see there is a v3, but the v3 does the same thing ...) Best regards, Maxime Devos. OpenPGP_

Re: [PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

itfall that could be mentioned in the docstring. Could be as simple as "No normalisation is performed.". I guess it shouldn't do normalisation, but guesswork seems better to be avoided/confirmed or disconfirmed when possible. Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH v4 4/4] load: Display modules depth in output when using %load-verbosely.

backwards-incompatible but I don't know any actual users of %load-hook etc. outside Guile itself. Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

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

netheless (to potentially replace Arne's implementation later, once it's complete), because it sounds like you might have avoided the REPR (*) bug thing from Arne's implementation. (*) Extremely unlikely to be a problem in practice, but still a bug. Best regards, Maxime Devos. Op

Re: Hygienic rewrite of (ice-9 expect)

sorry for that, but I'm out of here and will leave further review/applying/... to the maintainers and random guile-devel visitors. Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH v2] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

files, but, err, nope, copyright != author and likewise initial author != all authors) (*). Also, according to HACKING, you should be self-congratulatory, i.e., add yourself to THANKS. Other than that, I have no remarks. Best regards, Maxime Devos (*) It says (paraphrases) ‘see maintain.texi for w

Re: [PATCH v4 4/4] load: Display modules depth in output when using %load-verbosely.

w-other-keys). I think it's quite plausible that there will be more such arguments in the future! Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: [PATCH v2] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

Op 03-10-2023 om 20:56 schreef Dale Mellor: On Tue, 2023-10-03 at 20:49 +0200, Maxime Devos wrote: subtle spelling error: subtleties -> subtleties That's pretty subtle! Oops, I corrected the spelling error too early: subtelties -> subtleties OpenPGP_0x49E3EE221

Re: [PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

Op 03-10-2023 om 22:03 schreef Vivien Kraus: Hello! Le lundi 25 septembre 2023 à 22:46 +0200, Maxime Devos a écrit : However, there are also some dangers on doing this thing -- the ‘external’ pagehttps://example.com/data.json  could redirect to http://localhost/unsecured-secret-but-its

Re: [PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

cient, because there could be a DNS record that points 'website via http' to 127.0.0.1, and hence a redirect from https://website --> http://website can change IP addresses from global Internet to local computer. Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description:

Re: [PATCH v4 4/4] load: Display modules depth in output when using %load-verbosely.

he load hook, as far as I can tell. More concretely, as I understand it, all you need to do on the C-side is replacing > + scm_call_2(hook, full_filename, depth); by > + scm_call_3(hook, full_filename, scm_from_utf8_keyword("depth"), depth); (using SCM_KEYWORD inst

Re: [PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2.

Op 04-10-2023 om 07:29 schreef Vivien Kraus: Le mercredi 04 octobre 2023 à 00:30 +0200, Maxime Devos a écrit :       The best prevention is not allowing redirects at all or only       allowing redirections that keep the hostname intact -- while an       option for much software, it isn&#

Re: [BUG] Non-local exit in thunk from system-async-mark doesn't restore asyncs block

Op 06-10-2023 om 06:50 schreef Andrew Tropin: TLDR: abort-to-prompt restores asyncs block level. abort-to-prompt from a procedure scheduled with system-async-mark doesn't restort asyncs block level. Looks like a duplicate or variant of to me

Re: [PATCH v4 4/4] load: Display modules depth in output when using %load-verbosely.

Op 11-10-2023 om 04:36 schreef Maxim Cournoyer: Onderwerp: Re: [PATCH v4 4/4] load: Display modules depth in output when using %load-verbosely. Van: Maxim Cournoyer Datum: 11-10-2023 04:36 Aan: Maxime Devos CC: guile-devel@gnu.org Hi Maxime, Maxime Devos writes: [...] I now see

Re: [PATCH] doc: Extend documentation for (ice-9 match)

o to inline it or not, please do it consistently. (I know this doesn't quite answer the implicit question, but I don't have an answer.) Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: Hygienic rewrite of (ice-9 expect)

ng to personally not being able to figure out what to do with the patches, I wasn't referring to some specific technical issue. Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: automake test driver for Guile scheme patch review

x package, albeit not the best example because both are Guix.) If you retry merging it into Automake, I recommend picking up the new version from Guix. Best regards, Maxime Devos OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: Hygienic rewrite of (ice-9 expect)

Op 18-11-2023 om 12:29 schreef Daniel Dinnyes: Hi Maxime, I am still not sure I understand what you meant. You've said you weren't referring to technical issue, but also that you "get stuck in some vague loop of sorts and can't figure out what the maybe-issue is". Regarding what to do with

Re: automake test driver for Guile scheme patch review

Op 20-11-2023 om 17:16 schreef Timothy Sample: Hi, Maxime Devos writes: Op 19-11-2023 om 18:17 schreef Karl Berry: Hello Guile folk - back in May 2016, Mathieu Lirzin submitted a patch to add a test driver for Guile Scheme to Automake. https://lists.gnu.org/archive/html/automake-patches

Re: automake test driver for Guile scheme patch review

Op 21-11-2023 om 18:33 schreef Maxime Devos: I think that doing nothing other than closing that patch would be a reasonable course of action.  :) And how is "doing nothing" supposed to help with discoverability, ease of updating the test driver, clarity, unbundling and the goal

Re: [PATCH v2] doc: Document SRFI 64.

in the texi. Haven't looked at the actual documentation. Best regards, Maxime Devos. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

Re: automake test driver for Guile scheme patch review

Op 22-11-2023 om 00:02 schreef Timothy Sample: Hello, [Dropping Karl since we are no longer discussing Automake maintenance.] Maxime Devos writes: [What about] discoverability, ease of updating the test driver, clarity, unbundling and the goals of Freja Nordsiek? Maybe Guile should

Re: [PATCH v2] doc: Document SRFI 64.

+@c This SRFI 64 documentation was "snarfed" from upstream specification +@c HTML document using the 'snarfi' script. That HTML document comes with a license that requires: > The above copyright notice and this permission notice shall be > included in all copies or substantial portions of the

Re: [PATCH] Add more detailed instructions into the HACKING file.

. You might want to check if static libraries are built by default (*), and if so, add --disable-static to reduce compilation time. (*) can be tested with "find . -name '*.a'" after "make" -- don't worry about libgnu.a, IIUC only libguile-3.0.a / .so is impo

Re: [PATCH] Add more detailed instructions into the HACKING file.

Op 05-12-2023 om 00:12 schreef Tomas Volf: Thank you for the review. On 2023-12-04 22:06:42 +0100, Maxime Devos wrote: Op 29-11-2023 om 17:40 schreef Tomas Volf: +guix shell -D -f guix.scm --pure -- ./configure --enable-mini-gmp Also -fexcess-precision=standard (see #49368 / #49659

RE: Custom HTTP methods in web module

e “conform to grammar” part, not the “buffer size part”) (With regards to the first point) this paragraph SHOULD be ignored, this way leads to continued violations of the grammar and potential security problems (see example in previous point). Postel’s law is a mistake. Best regards, Maxime Devos

RE: Custom HTTP methods in web module

Not Allowed) status code. Given the proposal to (in this procedure) allow all methods (at least all grammatical methods) in a new implementation, it seems this won’t be this method’s responsibility anymore, though. Best regards, Maxime Devos

RE: Custom HTTP methods in web module

amiliar enough with the Guile implementation to tell if the extra logic is best done in this function or in its caller. It just needs to be done _somewhere_. Best regards, Maxime Devos

RE: Non-blocking web server

). I’ve only used it for demo purposes so far, though. Best regards, Maxime Devos.

RE: How to get pull-request feedback

annah and without any kind of administration – I just send patches to guile-devel@gnu.org with a cover message. (Or without cover message if it’s just a single patch.) Best regards, Maxime Devos.

RE: Allowing extended HTTP methods

callers may need to do extra validation. Also, the commit message needs to be changed to changelog format. Also worth checking if the Texinfo documentation mentions parse-http-method, and if so, adjust it. Best regards, Maxime Devos.

RE: The case for more macro-instructions?

ule2.go”, ... be a symlink to “module0.go” Some care required for targets not supporting symlinks, but making fake symlinks as regular files recognised by module loading code (or on lower level, whatever) should be straightforward. Best regards, Maxime Devos.

RE: exception from inside false-if-exception?

[Adding Andy Wingo because of the stack shenanigans] >Subject: exception from inside false-if-exception? Duplicate of #46009 - (backtrace) crash, string->number: Wrong type argument in position 1 (expecting string): #f - GNU bug report logs >the expression pointed to by debug.scm,72:40 is this:

RE: exception from inside false-if-exception?

eption handler stack (IIRC, Guile uses the more general fluid stuff instead because of this), but otherwise, I don’t think so. I think the problem is just a bug (and some of the with-throw-handler stuff that’s making thinking about what’s correct/implementing stuff correctly harder). Best regards, Maxime Devos

RE: [PATCH] Make get-bytevector-all suspendable.

I sense a lack of tests for the test suite ... Also, to avoid avoidable allocations and copying, it would be nice if %initial-length could be overridden (optional #:initial-length keyword argument), in case the user has a better guess available. Best regards, Maxime Devos

RE: [PATCH] Make get-bytevector-all suspendable.

Adding to my previous response: Most (all?) tests for suspendable/non-suspendable are shared, and run in both cases, so probably the suspendable get-bytevector-all already has tests.

RE: [PATCH] add SRFI-119 / language/wisp to Guile? (new patch withmore tests, squashed)

>where is the doc of Wisp? i did not yet install it, as i understand it will be >included in next release of Guile? Going by the the commit message, it now is in: > * doc/ref/srfi-modules.texi (srfi-119): add node

RE: Licensing of Guile code loaded by libguile.so

“L” to “GPL” appeared to lead to significant improvement that surpasses the cost of having more proprietary software. It’s not something I have carefully investigated, so take it with a full salt shaker. Best regards, Maxime Devos

RE: [PATCH] Make get-bytevector-all suspendable.

onsider the situation where the handler invokes the delimited continuation twice. (call-with-prompt [tag + handler things] (lambda () (get-bytevector-all [...])) [tag + handler things]) Thread #2: (system-async-mark (lambda () (abort-to-prompt [tag + more arguments])) [Thread #1])) Best regards, Maxime Devos.

RE: exception from inside false-if-exception?

is a rather recent commit). It would be helpful to include in test.scm what the expected output would be and what unexpected output is encountered. Best regards, Maxime Devos.

RE: exception from inside false-if-exception?

exception handler. I don’t know what you are investigating precisely, but maybe it is >https://sources.debian.org/src/guix/1.4.0-6/gnu/build/shepherd.scm/?hl=112#L109 If it is this, surely (@ (fibers) sleep) could be adjusted to _not_ suspend (and instead just, well, sleep) when there is no Fibers task scheduler (similar stuff exists for the (Fibers) channels and conditions implementation). Best regards, Maxime Devos.

RE: exception from inside false-if-exception?

e reason, the abort-to-prompt will succeed but any attempt to resume the >continuation (by calling it) would fail. This is because composing a saved >continuation with the current continuation involves relocating the stack >frames that were saved from the old stack onto a (possibly) new position on >the new stack, and Guile can only do this for stack frames that it created for >Scheme code, not stack frames created by the C compiler. It’s a bit gnarly but >if you stick with Scheme, you won’t have any problem. > >If no prompt is found with the given tag, this procedure just returns #f. Best regards, Maxime Devos.

RE: Define works different when Compile and Eval

no lambdas are returned. Best regards, Maxime Devos.

RE: Define works different when Compile and Eval

> > > if you want this^ to be actually defined while compilation is > > > happening (i.e. in the compilation stage; see staged computing), then > > > you need to use an (eval-when (expand) ...) wrapper around it. > > > > Thank you for the reply! Not sure what you mean. The following code > > defi

RE: what to do about gnulib

ory-name-here/autopoint” and add “insert-directory-name-here” to path, so no replacing .m4 happens. Best regards, Maxime Devos

RE: [PATCH 1/3] Make string-length documentation more correct

string >Returns the number of characters in the given string. , not “return the number of bytes”. Without mentioning the encoding, the “number of bytes” would be ill-defined anyways. Best regards, Maxime Devos.

RE: [BUG] Eval sets incorrect runtime metainformation

dure you can insert some meta-data for use by your run-time, in an initial vector alist. See https://www.gnu.org/software/guile/manual/html_node/Procedure-Properties.html. But that's limited and doesn't take macros, etc into account. That’s the job of ‘eval’, not the user of ‘eval’. Best regards, Maxime Devos.

RE: [PATCH 1/3] Make string-length documentation more correct

ight be interpreted in terms of some 8-bit encoding. Here’s a test: if you can input #\👨‍🏭 without errors and it evaluates to #\👨‍🏭, then the encoding should be set up correctly. Best regards, Maxime Devos

RE: [PATCH 1/3] Make string-length documentation more correct

>ISTR that "Unicode character" is actually synonymous the same than "Unicode code point" -- but the common meaning of "character" is more fuzzy. Perhaps it's wise to avoid that word when trying to be precise. My second point was that it is to late for that, unless you intend to rename procedures

RE: [PATCH 1/3] Make string-length documentation more correct

>No; he wrote é, U+0065 LATIN SMALL LETTER E + U+0301 COMBINING ACUTE ACCENT, >which is two characters unlike é, LATIN SMALL LETTER E WITH ACUTE. > >Likewise 👨‍🏭 is U+1F468 MAN + U+200D ZERO WIDTH JOINER + U+1F3ED FACTORY. Right, I should have tested that instead of assuming it’s the pre-combined

RE: The Guile junk drawer and a C plea (was: [PATCH] Addnondestructive delq1, delv1, and delete1.)

hings yet. For the embedded language case, it would be useful to have such an automatic generator. Best regards, Maxime Devos.

RE: The Guile junk drawer and a C plea (was: [PATCH] Addnondestructive delq1, delv1, and delete1.)

Coq itself or a selection of Coq libraries, but the point stands either way. Also, in RnRS modules can have version modules. There isn’t currently support for defining multiple versions of modules in Guile, but there could be. Best regards, Maxime Devos.

RE: The Guile junk drawer and a C plea

>Maxime Devos writes: >>> I suggest that we design a new module hierarchy, introduce aliases for >>> module bindings, and still supply the old module hierarchy during a few >>> years for backward compatibility. >> Also, on deprecation and removal: just because

RE: The Guile junk drawer and a C plea

languages that also include a couple of imported modules(and which these are depend on the precise fake language), though I don’t see why not just import those as modules), but that doesn’t mean we should repeat Racket’s mistakes with what else (and how) it also uses #lang for. Best regards, Maxime Devos

RE: [BUG] Eval sets incorrect runtime metainformation

applies to the ‘syntax’ route as well, unless you are doing complicated (but possible!) DIY partial macro expansion shenanigans.) Best regards, Maxime Devos.

RE: The Guile junk drawer and a C plea

>Maxime Devos writes: >> ``` >> #!r6rs >> (library (foo) >>(export foo) >>(import (rnrs base)) >>(define foo >> (cons 'a 1))) >> ``` > Here you are demonstrating how R6RS libraries have the _same_ problem. You > shoul

RE: The Guile junk drawer and a C plea

Sent from Mail for Windows From: Dr. Arne Babenhauserheide Sent: Sunday, 30 June 2024 16:34 To: Maxime Devos Cc: Philip McGrath; mik...@djurfeldt.com; Thompson, David; Richard Sent; guile-devel Subject: Re: The Guile junk drawer and a C plea >Maxime Devos writes: >> No it doesn’t, b

RE: [BUG] Eval sets incorrect runtime metainformation

ng precisely, as long are there is a path from ‘language -> Tree-Il’. Best regards, Maxime Devos.

RE: Improving the handling of system data (env, users, paths, ...)

s that there now are two string-ish object types, but since the two types represent different situations, one of them requires more care than the other, and many operations are supported for both, I don’t think that’s too bad. (It might also be possible to replace directly by a bytevector, but if you do this, then remember that on the C level you need to deal with the lack of trailing \0.) Best regards, Maxime Devos.

RE: Improving the handling of system data (env, users, paths, ...)

bytevector->string (well, you need to turn the single character into a string consisting of a single character first, but this is trivial, simply do (string [insert-character-here])). > returning the length of a string in characters, etc.? AFAIK, libiconv > doesn't provide these facilities. This is a basic string API, just do string-length like in (all?) Schemes. In Scheme, strings consists of characters, so string-length returns the length of a string in characters. Best regards, Maxime Devos.

RE: Improving the handling of system data (env, users, paths, ...)

or do Latin-1). Also, this structure makes no sense. Even if I did not provide an alternative solution of my own, that wouldn’t mean Emacs’s thing is the answer. (Negative) criticism can be valid without providing alternatives. Best regards, Maxime Devos.

RE: The Guile junk drawer and a C plea

time. The ‘burden’ that would be referred to, is not some oil to applied or gears to regularly replace, but rather a cleaning up past mistakes (once per mistake) that probably could have been prevented in the first place. Best regards, Maxime Devos.

RE: The Guile junk drawer and a C plea

ample. > [...] > > and this is the reason i spoke up in this thread, not to argue for > indiscriminate > cleanups. retaining an ice-9 compatibility falls into the kludge category, > i.e. it's ok if > it's clearly marked as a kludge, and if it incurrs little extra maintenance > costs. Nowhere did I say anything about not properly deprecating ‘define-module’. Best regards, Maxime Devos

RE: Name of the standard library

under the same module name) (I don’t know if this is the case), keeping it under (sxml ...) would make sense. (If not, (guile sxml ...)?) Best regards, Maxime Devos

RE: Name of the standard library

ocumentation what this _something_ is seems pretty reasonable to me (not a non-sequitur). Best regards, Maxime Devos.

RE: Name of the standard library

tioned earlier, I also want to mention that (srfi srfi-N) is not portable, it’s a Guile-ism.) (*) and for small Schemes where the RnRS / SRFI stuff is implemented as a RnRS library importing only standard RnRS modules. Best regards, Maxime Devos.

RE: Name of the standard library

>Is (import (srfi :N)) portable in practice? I don’t know. I know that (srfi srfi-N) isn’t portable, but I don’t know what _is_ portable. I don’t know if ‘(import ...)’ is standard either (sure it is as part of ‘define-library’, but I didn’t find it on its own in r7rs.pdf), That said, at leas

RE: Name of the standard library

can simply be name (even when it also is other things). That alternate universes are a hobby doesn’t prevent them from being illustrative. Best regards, Maxime Devos.

RE: Portable imports

-N) (in define-module) would be compatible, but that does not seem to be the future. Best regards, Maxime Devos

RE: Portable imports

>R7RS talks about "programs" and "libraries". These are technical terms with precise meanings. >A "program" corresponds to your typical Scheme script. IIRC it _has_ to start with (import ...). I’ve found it in r7rs.pdf now: > 7.1.6. Programs and definitions > → + +

RE: Encoding library names

oding the slash solves this easily. See above for how percent-encoding is a problem of its own. Best regards, Maxime Devos

RE: Type declarations and data validation utils?

front and the code ‘foo-error1’ and ‘foo-error2’ for constructing the condition object (and raising it) doesn’t need to be duplicated ... Best regards, Maxime Devos

RE: Are library names data or syntax?

n, it’s not much of a stretch to potentially also include lexical information, so perhaps numbers would work just fine too! (Implementation-dependent, but ‘multiple module namespaces’ and ‘define-library as a macro’ are also implementation-dependent.) Best regards, Maxime Devos.

RE: Numbers in library names

the SRFI-0 >> convention of "srfi-N" names, which is basically also used by Guile. > >Aesthetics matter. That’s one reason why I would prefer (srfi |1|) or (srfi srfi-1). That lone number next to an identifier in (srfi 1) is unaesthetic to me. Best regards, Maxime Devos.

RE: [PATCH] doc: Mention how to remove namespaces in xml->sxml.

t still work then? (I can imagine that somewhere the SXML code assumes a unique ‘namespace symbol/#f’ -> ‘namespace URL’ mapping.) Best regards, Maxime Devos.

RE: Numbers in library names

s a practical concern. (More precisely: lexical context of library name not necessarily the same as context of a name part.) This is irrelevant to Guile though, Guile doesn’t have this extension. Regards, Maxime Devos

RE: Numbers in library names

> If (srfi |1|) were to be standardised via SRFI process or RnRS (maybe > implicitly as a ‘module names equality is to be done modulo > number/symbol conversions’ thing in a future R8RS), then (srfi |1|) > would be fine, but such a thing. Looks like I didn’t finish the sentence: ‘but such a thi

RE: Lexically bound macro, with lexically bound transformer

n variables bound by syntax-case. It does >not currently capture local syntax transformers bound by let-syntax,  >letrec-syntax or non-top-level define-syntax forms. Any attempt to reference >such captured syntactic keywords via local-eval or local-compile produces an >error. The ques

RE: Making code compatible with different versions of Guile— #:declarative?

omment on what the default _should_ be.) Best regards, Maxime Devos.

RE: Exporting a nonexistent variable

h.) Best regards, Maxime Devos

<    1   2   3   4   >