mirror of
https://github.com/neovim/neovim.git
synced 2025-09-28 14:08:32 +00:00
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
6fdb628082
Co-authored-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com>
This commit is contained in:
@@ -2078,7 +2078,7 @@ void ex_loadkeymap(exarg_T *eap)
|
||||
char buf[KMAP_LLEN + 11];
|
||||
char *save_cpo = p_cpo;
|
||||
|
||||
if (!getline_equal(eap->getline, eap->cookie, getsourceline)) {
|
||||
if (!getline_equal(eap->ea_getline, eap->cookie, getsourceline)) {
|
||||
emsg(_("E105: Using :loadkeymap not in a sourced file"));
|
||||
return;
|
||||
}
|
||||
@@ -2094,7 +2094,7 @@ void ex_loadkeymap(exarg_T *eap)
|
||||
|
||||
// Get each line of the sourced file, break at the end.
|
||||
while (true) {
|
||||
char *line = eap->getline(0, eap->cookie, 0, true);
|
||||
char *line = eap->ea_getline(0, eap->cookie, 0, true);
|
||||
|
||||
if (line == NULL) {
|
||||
break;
|
||||
|
Reference in New Issue
Block a user