pg: do not turn off warnigns artificially

Compiler warnings often mean something, fiddling with them is not good
practise.  Besides the 'proglem' removed macro tried to 'fix' does not
even occur when compiling with modern gcc.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
This commit is contained in:
Sami Kerola 2012-10-08 08:08:15 +01:00 committed by Karel Zak
parent 69f3ff5e7e
commit 7d35cf4e57
1 changed files with 0 additions and 21 deletions

View File

@ -70,11 +70,6 @@
#define CMDBUF 255 /* size of command buffer */
#define TABSIZE 8 /* spaces consumed by tab character */
/*
* Avoid the message "`var' might be clobbered by `longjmp' or `vfork'"
*/
#define CLOBBGRD(a) (void)(&(a));
#define cuc(c) ((c) & 0377)
enum { FORWARD = 1, BACKWARD = 2 }; /* search direction */
@ -986,22 +981,6 @@ pgfile(FILE *f, const char *name)
*/
FILE *fbuf, *find, *save;
/* silence compiler - it may warn about longjmp() */
CLOBBGRD(line);
CLOBBGRD(fline);
CLOBBGRD(bline);
CLOBBGRD(oldline);
CLOBBGRD(eofline);
CLOBBGRD(dline);
CLOBBGRD(ttycols);
CLOBBGRD(search);
CLOBBGRD(searchcount);
CLOBBGRD(seekeof);
CLOBBGRD(eof);
CLOBBGRD(fpos);
CLOBBGRD(nobuf);
CLOBBGRD(fbuf);
if (ontty == 0) {
/*
* Just copy stdin to stdout.