From 21e27da70d25773bc6c271b8ae3885b20974e779 Mon Sep 17 00:00:00 2001 From: Steven Allen Date: Fri, 13 Jun 2025 07:51:37 -0700 Subject: [PATCH] Improve documentation of the internal Lisp_Process->status field Contrary to the existing documentation here, the value of this field cannot be the symbols open or closed. Furthermore, this field is never set to "stop" for network connections. * src/process.h (Lisp_Process): Improve/fix documentation of the 'status' field. (Bug#78784) (cherry picked from commit 4d88b925ba839fab9448915edcc699a6647df71c) --- src/process.h | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/src/process.h b/src/process.h index a27e95a9199..1e0ad8c7f68 100644 --- a/src/process.h +++ b/src/process.h @@ -83,13 +83,20 @@ struct Lisp_Process Lisp_Object mark; /* Symbol indicating status of process. - This may be a symbol: run, open, closed, listen, or failed. + This may be a symbol: run, listen, or failed. Or it may be a pair (connect . ADDRINFOS) where ADDRINFOS is a list of remaining (PROTOCOL . ADDRINFO) pairs to try. Or it may be (failed ERR) where ERR is an integer, string or symbol. Or it may be a list, whose car is stop, exit or signal and whose cdr is a pair (EXIT_CODE . COREDUMP_FLAG) - or (SIGNAL_NUMBER . COREDUMP_FLAG). */ + or (SIGNAL_NUMBER . COREDUMP_FLAG). + The symbols open and closed are not used here: an open network + process has an internal status of "run" and a closed network + process an internal status of "exit". + Stopped network processes do not set this status to "stop"; + instead, they set command to t. "stop" is only used here to + indicate stopped system processes. + */ Lisp_Object status; /* Coding-system for decoding the input from this process. */ -- 2.39.5