COMMAND$ and wildcards on files
#11
It still feels like it is easier to have all those files already provided to you by the logic of COMMAND$ rather than trying to build your own recursion. I think a user expects that if they supply *.* then it means all files. Unless there is something special you're trying to do with that.
Ask me about Windows API and maybe some Linux stuff
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 SpriggsySpriggs - 12-30-2022, 05:58 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-30-2022, 06:11 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: 6 Guest(s)