aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/health.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2024-04-13 06:39:30 +0800
committerGitHub <noreply@github.com>2024-04-13 06:39:30 +0800
commit4f3d018d15d299b66a341bed4d677d7ec03ad44f (patch)
treee79ecb738cb33e606495e141054c184a8e1caf6a /runtime/lua/vim/health.lua
parent64aa0f7d0b7034a5158401cf6b987cb82cc60031 (diff)
downloadrneovim-4f3d018d15d299b66a341bed4d677d7ec03ad44f.tar.gz
rneovim-4f3d018d15d299b66a341bed4d677d7ec03ad44f.tar.bz2
rneovim-4f3d018d15d299b66a341bed4d677d7ec03ad44f.zip
vim-patch:9.0.2180: POSIX function name in exarg causes issues (#28308)
Problem: POSIX function name in exarg struct causes issues on OpenVMS Solution: Rename getline member in exarg struct to ea_getline, remove isinf() workaround for VMS There are compilers that do not treat well POSIX functions - like getline - usage in the structs. Older VMS compilers could digest this... but the newer OpenVMS compilers ( like VSI C x86-64 X7.4-843 (GEM 50XB9) ) cannot deal with these structs. This could be limited to getline() that is defined via getdelim() and might not affect all POSIX functions in general - but avoiding POSIX function names usage in the structs is a "safe side" practice without compromising the functionality or the code readability. The previous OpenVMS X86 port used a workaround limiting the compiler capabilities using __CRTL_VER_OVERRIDE=80400000 In order to make the OpenVMS port future proof, this pull request proposes a possible solution. closes: vim/vim#13704 https://github.com/vim/vim/commit/6fdb6280821a822768df5689a5d727e37d38306c Co-authored-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com>
Diffstat (limited to 'runtime/lua/vim/health.lua')
0 files changed, 0 insertions, 0 deletions