https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96287
Andreas Urban changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96287
--- Comment #4 from Andreas Urban ---
Looking closer at how Perl exec works, along with join on empty strings and
variable, there would seem to be no problem:
exec 'gcc', join(' ', @cppflags, @cflags, '-o', '$@', '$<')
There may be one or two t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96287
--- Comment #3 from Andreas Urban ---
(In reply to Jonathan Wakely from comment #1)
> Ignoring it could lead to equally undesirable behaviour though.
>
> for file in *.cc ; do gcc "$fil" ; done
>
> Don't those languages support something like t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96287
--- Comment #2 from Andreas Schwab ---
If you pass a non-file-name where a file name is expected you are doing
something wrong, and you need to fix *that*. Hiding errors is doing a
disservice.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96287
--- Comment #1 from Jonathan Wakely ---
Ignoring it could lead to equally undesirable behaviour though.
for file in *.cc ; do gcc "$fil" ; done
Don't those languages support something like the Bourne shell's "$@" which does
the right thing?
