bug? in find

[Shigeru Mabuchi]

Hello,

  Thanks for your admiring works.

  I just found a fatal bug in the 'find' program and I
would like to let you know. I used 'find' to delete
out-of-dated files in my crontab and I happened to
find it not working in a case like this:

  IF THERE IS NO SUBDIRECTORY AT ALL IN THE PATH,
FIND RETURNS ERROR AS FOLLOW: 

find: paths must precede expression
Usage: find [path...] [expression]
  
  For example, if there are only files in the
directory /home/foo/obj,

  find /home/foo/obj -name *.o

returns the above error.

Instead,

  find /home/foo -name *.o

gives me the *.o list in /home/foo/obj.   

  I'm not sure if this is a part of the 'find'
specs, but even if it is so, I believe that it
should be corrected. At least the error message
should be something like 'no directory found'
if 'find' can only search directory in the top
level of the search path.

  Thanks.

Shigeru MABUCHI
WING
http://wing.gr.jp/