> > On 2008-09-25 at 14:06:57 [+0200], François Revol <revol@xxxxxxx> > wrote: > > > Howdy, > > > > > > as noted in #2770 our /bin/c++ wrapper script (which is identical > > > to > > > Be's > > > BTW) doesn't deal correctly with whitespace in path names. > > > Besides > > > that I > > > wouldn't even know how to do that in a shell script, does anyone > > > know > > > a > > > reason why the script is used at all? The shell variables for > > > additional C > > > or C++ flags are empty by default and I don't think I've ever > > > seen an > > > example where they are set. Unless there are objections, I would > > > simply > > > replace the script by a symlink to g++. > > > > I thought "$@" should actually work correctly with spaces... > > As is it doesn't, but I just learned, quoting it does -- i.e. it > doesn't > produce a single string as I would have expected. > Indeed it does. It's "$@" that is used in Zeta. François.