Steve Holden wrote: >"Fredrik Lundh" <fredrik at pythonware.com> wrote ... >> Paul Prescodwrote: >>> It's simply Windows versus Unix. On Unix the *shell* does >>> globbing. The program never sees the unexpanded filename. On >>> Windows, the application must do globbing (if it wants to). >> >> to be precise, it's a linking issue. to get globbing behaviour, >> just link the executable with setargv.obj (provided with visual >> C). >> >> for some reason, GvR didn't want this as a default. cannot recall >> his arguments, though... >> >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. Robert Amesz
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