Hi!

----

While doing some more cleanup in the tree I found the following "lint"
warnings for "comp/regexp.h" (these are the only warnings except
E_UNRECOGNIZED_PRAGMA_IGNORED):
-- snip --
$ cd usr/src/lib/libast/amd64
$ cat lint.out | fgrep -v "(E_UNRECOGNIZED_PRAGMA_IGNORED)"
"../common/", line 90: warning: implicit function declaration: GETC
(E_NO_IMPLICIT_DECL_ALLOWED)
"../common/comp/regexp.h", line 94: warning: implicit function
declaration: UNGETC (E_NO_IMPLICIT_DECL_ALLOWED)
"../common/comp/regexp.h", line 98: warning: implicit function
declaration: ERROR (E_NO_IMPLICIT_DECL_ALLOWED)
"../common/comp/regexp.h", line 99: warning: implicit function
declaration: RETURN (E_NO_IMPLICIT_DECL_ALLOWED)
"../common/comp/regexp.h", line 125: warning: function falls off bottom
without returning value: _re_read (E_FUNC_NO_RET_VAL)
"../common/comp/regexp.h", line 125: warning: Function has no return
statement : _re_read (E_FUNC_HAS_NO_RETURN_STMT)
-- snip --

This raises two questions:
- "comp/regexp.h" includes the comment "OBSOLETE: use <regex.h>" - does
that means this header will go away at some point ?
- How can I teach "lint" that "GETC"/"UNGETC"/"ERROR" and "RETURN" are
coming from the application side (see regexp(5)) ?

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)

Reply via email to