From 04ae56962e58a5d576412cc344e96159a6822e38 Mon Sep 17 00:00:00 2001 From: "Kent R. Spillner" Date: Wed, 13 Oct 2021 17:19:16 +0300 Subject: [PATCH] slightly tweak description of b_list in comments I noticed a small typo in the comment describing the use of b_list in struct basicblock_ ("... that the block are allocated"). Reviewing the other comments describing use of b_list I then noticed a slight inconsistency in the description of what it actually points to ("next," "early") which I also decided to address here. --- Python/compile.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Python/compile.c b/Python/compile.c index 0c025acec149140..3131a67bcdbe230 100644 --- a/Python/compile.c +++ b/Python/compile.c @@ -134,8 +134,9 @@ is_jump(struct instr *i) typedef struct basicblock_ { /* Each basicblock in a compilation unit is linked via b_list in the - reverse order that the block are allocated. b_list points to the next - block, not to be confused with b_next, which is next by control flow. */ + reverse order that blocks are allocated. b_list points to the previously + allocated block, not to be confused with b_next, which is next by control + flow. */ struct basicblock_ *b_list; /* number of instructions used */ int b_iused; @@ -221,7 +222,7 @@ struct compiler_unit { Py_ssize_t u_posonlyargcount; /* number of positional only arguments for block */ Py_ssize_t u_kwonlyargcount; /* number of keyword only arguments for block */ /* Pointer to the most recently allocated block. By following b_list - members, you can reach all early allocated blocks. */ + members, you can reach all previously allocated blocks. */ basicblock *u_blocks; basicblock *u_curblock; /* pointer to current block */