Bug 437750

Description of problem:
An directory arg stops processing

Version-Release number of selected component (if applicable):
gawk-3.1.5-15

How reproducible:
Always

Steps to Reproduce:
1. In an empty directory ...
2. for f in a c e; do echo >$f; done
3. mkdir b
4. awk --compat '{print FILENAME}' *

Actual results:
a
awk: cmd. line:1: fatal: file `b' is a directory

Expected results:
a
c
e

Additional info:
The existence of a directory might produce a warning on stderr but it certainly
shouldn't stop processing of other files.  Mainly because it is a HUGE
incovenience if you have a directory of 1000 files and one sub-directory and you
have to resort to some weird command like: awk '{print FILENAME}' `find .
-maxdepth 1 -type f`

On SunOS and many other unix's traditional awk silently skips directories, which
is very sensible behavior indeed.  Because if awk doesn't process a directory
(it cannot) and therefore doesn't do anything with it (it cannot) then why
should it loudly proclaim an error and completely abort?  It is quite safe to
continue processing other args because the directory is not affected one way or
another.

Look at any other programs and see how directories are handled. None of vi, wc,
cat, etc completely abort processing just because they encounter a directory.

This also happens regardless of use of --compat option. Despite the
documentation claiming "... in compatibility mode, gawk behaves identically to
UNIX awk ...". That is clearly untrue.