From: Andrew Tropin <andrew@trop.in>
To: guile-devel@gnu.org
Cc: Andrew Tropin <andrew@trop.in>
Subject: [PATCH 2/3] Change make-dynamic-state mentions to current-dynamic-state
Date: Tue, 25 Jun 2024 15:20:11 +0400 [thread overview]
Message-ID: <20240625112221.15576-3-andrew@trop.in> (raw)
In-Reply-To: <20240625112221.15576-1-andrew@trop.in>
* doc/ref/api-scheduling.texi:
* libguile/fluids.c:
---
doc/ref/api-scheduling.texi | 2 +-
libguile/fluids.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ref/api-scheduling.texi b/doc/ref/api-scheduling.texi
index d79808049..f6cc942a1 100644
--- a/doc/ref/api-scheduling.texi
+++ b/doc/ref/api-scheduling.texi
@@ -199,7 +199,7 @@ A fluid created with @code{make-thread-local-fluid} won't be captured by
Return a newly created fluid, whose initial value is @var{dflt}, or
@code{#f} if @var{dflt} is not given. Unlike fluids made with
@code{make-fluid}, thread local fluids are not captured by
-@code{make-dynamic-state}. Similarly, a newly spawned child thread does
+@code{current-dynamic-state}. Similarly, a newly spawned child thread does
not inherit thread-local fluid values from the parent thread.
@end deffn
diff --git a/libguile/fluids.c b/libguile/fluids.c
index ebdb48fbc..4632f32ae 100644
--- a/libguile/fluids.c
+++ b/libguile/fluids.c
@@ -264,7 +264,7 @@ SCM_DEFINE (scm_make_thread_local_fluid, "make-thread-local-fluid", 0, 1, 0,
"Return a newly created fluid, whose initial value is @var{dflt},\n"
"or @code{#f} if @var{dflt} is not given. Unlike fluids made\n"
"with @code{make-fluid}, thread local fluids are not captured\n"
- "by @code{make-dynamic-state}. Similarly, a newly spawned\n"
+ "by @code{current-dynamic-state}. Similarly, a newly spawned\n"
"child thread does not inherit thread-local fluid values from\n"
"the parent thread.")
#define FUNC_NAME s_scm_make_thread_local_fluid
--
2.45.1
next prev parent reply other threads:[~2024-06-25 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 11:20 [PATCH 0/3] Documentation improvements Andrew Tropin
2024-06-25 11:20 ` [PATCH 1/3] Make string-length documentation more correct Andrew Tropin
2024-06-25 11:27 ` Maxime Devos
2024-06-26 11:18 ` Andrew Tropin
2024-06-26 11:46 ` Maxime Devos
2024-06-26 12:07 ` tomas
2024-06-26 12:09 ` Maxime Devos
2024-06-26 12:18 ` Jean Abou Samra
2024-06-26 12:26 ` Maxime Devos
2024-06-26 14:47 ` Damien Mattei
2024-06-28 13:42 ` Andrew Tropin
2024-06-28 13:38 ` Andrew Tropin
2024-06-25 11:20 ` Andrew Tropin [this message]
2024-06-25 11:20 ` [PATCH 3/3] Fix spelling Andrew Tropin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240625112221.15576-3-andrew@trop.in \
--to=andrew@trop.in \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).