Bug 79626

Description of problem:

$ help for
for: for NAME [in WORDS ... ;] do COMMANDS; done
    The `for' loop executes a sequence of commands for each member in a
    list of items.  If `in WORDS ...;' is not present, then `in "$@"' is
    assumed.  For each element in WORDS, NAME is set to that element, and
    the COMMANDS are executed.

now, look how it really works.

$ cat fortest1.sh 
#!/bin/bash1
for x
  do echo foo "${x}"
done

$ cat fortesta.sh 
#!/bin/bash-2.05a
for x
  do echo foo "${x}"
done

$ cat fortestb.sh 
#!/bin/bash-2.05b
for x
  do echo foo "${x}"
done

$ ./fortest1.sh worked since the \'90s
foo worked
foo since
foo the
foo '90s

$ ./fortesta.sh works very well
foo works
foo very
foo well

$ ./fortestb.sh breaks insanely
foo 
$

examples of ways this bash version breaks in the real life:

$ libtoolize --help
libtoolize: too many arguments
Try `libtoolize --help' for more information.

and when using "libtool --debug *anything*", I get:
+ echo 'libtool: compile: cannot determine name of library object from `'\'''
libtool: compile: cannot determine name of library object from `'

for vim:
$ ./configure
configure: error: can not find sources in auto or ..



Version-Release number of selected component (if applicable):
2.05b-5

How reproducible:
100.000%

Steps to Reproduce:
1. use for-loop without "in WORDS ..."
2. cry
    
Actual results:
every parameter ("$@") is ignored

Expected results:
not ignoring, like older versions of bash (working as documented by the help)

Additional info:
I saw similar bug at debian bug tracking database some weeks/months ago