bug or feature: `eval' vs `#!'

[Jerome BENOIT]

> >Hello:
> >
> >Under Win98 script files with as first line
> >
> >eval '(exit $?0)' && eval 'exec perl -S $0 ${1+"$@"}' && eval 'exec perl
> >-S $0 $ argv:q'
> >
> >contrary to script files with bang mechanism (`#! <executable>')
> >are not identify as executable (and we cannot set them executable with
> >`chmod'),
> >and therefore the completion mechanism does NOT work for them.
> >
> >
> >
> >Is it a bug or a feature ?
> >
> >Byebye,
> >Jerome BENOIT
> 
> Shell scripts that don't start with !# are inherently non-portable.  See
> 
> Why doesn't my script work?
> http://www.cygwin.com/faq/faq_toc.html#TOC39
> 
> in the FAQ.  Keep in mind, this is a great source of information for
> issues/questions like these!

The script works under Cygwin and its first line is said to be portable,
hence my question.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple