~ chicken-core (master) 1d5b96d455874beb5dde2321f24acb4e65f19eb5

commit 1d5b96d455874beb5dde2321f24acb4e65f19eb5
Author:     felix <felix@call-with-current-continuation.org>
AuthorDate: Wed Oct 29 11:29:23 2025 +0100
Commit:     felix <felix@call-with-current-continuation.org>
CommitDate: Wed Oct 29 11:29:23 2025 +0100

    Add comment about "scheme" module.

diff --git a/library.scm b/library.scm
index b507199d..b45c4d05 100644
--- a/library.scm
+++ b/library.scm
@@ -200,6 +200,15 @@ EOF
 ;; We get around this problem by using the "chicken.internal.syntax"
 ;; module, which is baked in and exports *every* available core macro.
 ;; See modules.scm, expand.scm and chicken-syntax.scm for details.
+;;
+;; NOTE #2: The module "scheme" is a legacy artifact, with CHICKEN
+;; 6 "scheme" being just an alias for "scheme.r5rs", and "scheme.base"
+;; is what used to be the standard Scheme module. We use it only
+;; to provide a prefix ("scheme#") for the exported toplevel
+;; identifiers, which now represent what is in the "scheme.base"
+;; standard module. Yes, this is somewhat confusing, but changing
+;; all prefixes to use the "proper" name would cause too many
+;; bootstrapping problems.
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 
 ;; Pre-declaration of scheme, so it can be used later on.  We only use