upvote

points

by mesrik5 hours ago |
comments
upvoteby mesrik3 hours ago|
next
[-]
Oh my, I'm sorry how many typos I made and forgot to fix.

s/ARAIC/AFAIC/g s/70kb/720kB/g

reply
upvoteby akdor11542 hours ago|
prev|
[-]
> under MS-DOS command line parsing was left completely to a a loaded program

And in the many decades and OS rewrites since, they have long since corrected this mistake... right?

reply
upvoteby mesrik2 hours ago|
parent|
next
[-]
I think I did have some time early -90's someone did alternative C0.lib which actually when you linked it with your programs it made much easier porting some *nix software to MS-DOS. No need to make modifications command line handler, as that modified startup-library as I think it's or was called, did what was needed.

It was then COMMAND.COM ie. Dos command line did not do that. And there were alternatives like something called 4DOS which I did never use, but those could have done it. Or did they?

I have't used Windows for quite long time. And I do not know if CMD.EXE or PowerShell whatever its name are any better. Maybe someone knowing would like to comment this.

reply
upvoteby contextfree41 minutes ago|
parent|
[-]
This isn't so much a cmd thing as a fundamental Windows API thing. CreateProcess takes in the entire command line as a single string.

Powershell is a completely different model where native commands run in-process, you can import commands and invoke APIs from arbitrary .NET assemblies, and then the PS runtime handles all argument parsing (and many other things). But it also lets you invoke and interop with arbitrary command-line executables and then those do their own parsing like they always have.

reply
upvoteby seritools55 minutes ago|
parent|
prev|
[-]
no, Windows still leaves that to the program. Usually handled by the msvc runtime for argv/argc, but the base windows API is GetCommandLine, giving you a single string.

EDIT: https://nullprogram.com/blog/2022/02/18/

reply