patch 9.0.2180: POSIX function name in exarg causes issues Commit: https://github.com/vim/vim/commit/6fdb6280821a822768df5689a5d727e37d38306c Author: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Date: Tue Dec 19 20:53:07 2023 +0100 patch 9.0.2180: POSIX function name in exarg causes issues 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: #13704 Signed-off-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>

/* XPM */
static char * tb_find_xpm[] = {
/* width height ncolors cpp [x_hot y_hot] */
"18 18 5 1 0 0",
/* colors */
" 	s none	m none	c none",
".	s iconColor1	m black	c #000000",
"X	s iconColor2	m none	c #FFFFFF",
"O	s iconGray2	m none	c #bdbdbd",
"+	s bottomShadowColor	m black	c #5D6069",
/* pixels */
"                  ",
" .........        ",
" .XXXXXXX..       ",
" .XXXXXXX.O.      ",
" .XXXXXXX....     ",
" .XXXXXXXXXX.     ",
" .XXXXXXX....     ",
" .XXXXXX.OOOO.    ",
" .XXXXX.OXXOOO.   ",
" .XXXXX.OXOOOO.   ",
" .XXXXX.OOOOOO.   ",
" .XXXXX.OOOXOO.   ",
" .XXXXXX.OOOO.+   ",
" .XXXXXXX....+..  ",
" .XXXXXXXXXX.+... ",
" ............+ .. ",
"    ++++++++++    ",
"                  "};