"Robert Amesz" ... > Steve Holden wrote: [ ... ] > > >Seems sensible since it's not the platform default for other command > >line programs? Nasty to have to glob wildcards, but consistent with > >the DOS heritage. > > Why nasty? This is one instance were I think UNIX has got it wrong. > It's much better to leave commandline parameters alone than to try and > interpret them in a particular way. Explicit is better than implicit. > Whichever way you write your programs you lose unless you specifically test the environment. If you glob by default then you end up globbing wildcard names which Unix users escaped because they wanted to refer to real files with wildcard characters in their names. But DOS/Windows works OK. If you *don't* glob by default then Unix works OK. But DOS/Windows passes you unglobbed names, expecting you to glob them, so you don't find the files. Perhaps I should have said "ugly"? The environments aren't consistent but-when-did-vendors-try-to-be-consistent-ly y'rs - [Ss][Tt][Ee][Vv][Ee]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4