req_warning is not really about regular warnings. This flag is set by
ERR_warning() while regular warnings are thrown using ERR_post_warning()
-- and it makes a lot of difference ;-)
ERR_warning() is only called from EVL_field() to produce a famous "no
current record for fetch operation" error. I honestly don't know why
such a weird solution was designed in this place. Maybe EVL_field()
could be originally called from the code paths not prepared to handle
exceptions gracefully, maybe some other reason exists (or existed
before). But we still have this code in place.
Dmitry