Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
COMMAND$ and wildcards on files
#14
The shell does what most users expect. Few people run "7z.exe" on Windows console, because it has other-wordly behavior with wildcards which is considered normal on Unix and descendants. For example, 7-Zip command-line program doesn't like "*.*", it prefers just "*" and warns about it in the manual.

Handling "*.*" especially should be to avoid system files. It should be also for reckless algorithms that expect a text file but is given a binary file instead and chokes on the multitude of ASCII0. But a program that employs such a scheme should be reserved for people who dedicate their time to breaking stuff instead of enjoying a game or a movie, accepting results of a computation, "safe and secure" for the administrator etc.
Reply


Messages In This Thread
COMMAND$ and wildcards on files - by zaadstra - 12-24-2022, 05:12 PM
RE: COMMAND$ and wildcards on files - by SMcNeill - 12-24-2022, 07:35 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 12-25-2022, 12:33 AM
RE: COMMAND$ and wildcards on files - by SMcNeill - 12-25-2022, 12:48 AM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-25-2022, 08:10 AM
RE: COMMAND$ and wildcards on files - by zaadstra - 12-25-2022, 04:23 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 12-29-2022, 05:58 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-30-2022, 01:01 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-30-2022, 06:11 PM
RE: COMMAND$ and wildcards on files - by mnrvovrfc - 12-30-2022, 11:25 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 01-17-2023, 10:12 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 01-19-2023, 05:25 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 01-19-2023, 05:59 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 01-19-2023, 07:31 PM



Users browsing this thread: 1 Guest(s)