adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

patch 9.1.1841: patch 9.1.1840 adds python build dependency

Browse Source 
Problem:  patch 9.1.1840 adds python build dependency
          (chdizza)
Solution: Update dependencies (Hirohito Higashi)

fixes: #18523
related: #18045
closes: #18527

Signed-off-by: Hirohito Higashi <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
Hirohito Higashi
2025-10-09 19:14:55 +00:00
committed by Christian Brabandt
parent e7c765fe59
commit ed93df4935
8 changed files with 157 additions and 156 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
runtime/doc/develop.txt
View File

@ -1,4 +1,4 @@
*develop.txt* For Vim version 9.1. Last change: 2025 Sep 29
*develop.txt* For Vim version 9.1. Last change: 2025 Oct 09
VIM REFERENCE MANUAL by Bram Moolenaar
@ -365,28 +365,17 @@ We follow POSIX.1-2001 (SUSv3) for type sizes, which in practice means:
FUNCTION PROTOTYPES *assumptions-prototypes*
Vim currently does not use conventional header files (`.h`) for most internal
function prototypes. Instead, the current architecture uses individual `.pro`
files in the `src/proto/` directory, with one `.pro` file per `.c` file.
Vim does not use conventional header files (`.h`) for most internal function
prototypes. Instead, the current architecture uses individual `.pro` files in
the `src/proto/` directory, with one `.pro` file per `.c` file.
Unlike traditional self-contained header files, these `.pro` files do not
contain API documentation, struct and enum definitions, or other declaration;
contain API documentation, struct and enum definitions, or other declarations;
only function prototypes.
The bundling of these files is not automated. The `src/proto.h` header is
composed of a list of manual `#include` directives, one for each individual
`.pro` file.
Due to this design, integrating a new source file within this architecture
involves creating a corresponding `.pro` file, manually adding a new `#include`
directive to `proto.h` and manually adding this file to both `src/Makefile` and
`src/Make_mvc.mak`.
A `make proto` target exists in `src/Makefile` with the original goal of
automating the process of updating the `.pro` files. However, this target is
unreliable, fails on major platforms (e.g., macOS), and is only part of the
new release workflow. In practice, contributors edit the relevant `.pro` files
by hand when adding, removing, or modifying a function signatures.
The `make proto` target in `src/Makefile` automates updating most of the .pro
files using the Python script proto/gen_prototypes.py, which relies on the
python3-clangd module. Note that a few proto files are hand edited.
This system has been in place since at least v1.24, when Vim's functions were
still written in K&R style.