On Sun, Jan 31, 2016 at 2:35 AM, h_east <[email protected]> wrote: > Hi Tony, > > 2016-1-31(Sun) 10:14:15 UTC+9 Tony Mechelynck: >> (When writing to Japanese posters, I never know which is the given >> name and which is the family name: I know that the Japanese custom is >> to put the family name first, but some Japanese people reverse their >> names when writing to "Western" people and some not, and I never know >> which is which. Please pardon me if I erred.) > > Please be assured that does not attack even by mistake :-) > My family name is Higashi. It means the east in English. > >> >> On Sun, Jan 31, 2016 at 1:55 AM, h_east <[email protected]> wrote: >> > Hi Tony, >> > >> > 2016-1-31(Sun) 8:21:26 UTC+9 Tony Mechelynck: >> >> At patchlevel 7.4.1219, I see the following messages in Tiny compile >> >> but not in Huge. They "may" be due to a different (recent but earlier) >> >> patchlevel: >> >> >> >> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall >> >> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_cmds.o >> >> ex_cmds.c >> >> ex_cmds.c: In function ‘ex_helptags’: >> >> ex_cmds.c:6600:14: warning: unused variable ‘files’ [-Wunused-variable] >> >> char_u **files; >> >> ^ >> >> ex_cmds.c:6599:10: warning: unused variable ‘filecount’ >> >> [-Wunused-variable] >> >> int filecount; >> >> ^ >> >> ex_cmds.c:6598:12: warning: unused variable ‘fname’ [-Wunused-variable] >> >> char_u fname[8]; >> >> ^ >> >> ex_cmds.c:6597:12: warning: unused variable ‘ext’ [-Wunused-variable] >> >> char_u ext[5]; >> >> ^ >> >> ex_cmds.c:6591:10: warning: unused variable ‘len’ [-Wunused-variable] >> >> int len; >> >> ^ >> >> ex_cmds.c:6590:13: warning: unused variable ‘j’ [-Wunused-variable] >> >> int i, j; >> >> ^ >> >> ex_cmds.c:6590:10: warning: unused variable ‘i’ [-Wunused-variable] >> >> int i, j; >> >> ^ >> >> ex_cmds.c:6589:14: warning: unused variable ‘ga’ [-Wunused-variable] >> >> garray_T ga; >> >> ^ >> >> >> >> >> >> I don't know why the message seem to be produced in random order >> >> relative to the source. I suppose that there are missing #ifdef lines, >> >> and that the resulting executable will be OK. >> > >> > I reproduce it. >> > An attached patch fixing this. >> >> Dear Hirohito, maybe you attached a patch, but it wasn't in the >> message which reached me. > > Oops, Now surely attached. > Thanks. > -- > Best regards, > Hirohito Higashi (a.k.a h_east) > With this patch applied, the Tiny build compiles with no warnings. Thanks!
Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
