ebsh wrote
> The method name suggests that it doesn’t work on windows.
The method name "unixCmd" is purely historical, from a time when SC existed
only for Mac and the only system commands you could execute were Unix ones.
When the first Windows version arrived, the developer who ported it *did*
write a primitive to forward DOS shell commands to the system... but (for
good or ill) kept the name "unixCmd" and now we're kind of stuck with it.
So... you *can* do
"dir".unixCmd
... in Windows and it will work. "dir" isn't Unixy, but in this case you
have to read the code the way computers do, not the way humans do.
Devs: Maybe it's time finally to deprecate and rename it? This bit of
folklore ("'unixCmd' isn't for Windows") just won't die... and it's because
we're keeping a semantically incorrect method name around.
The two methods should really be called "asyncSystemCmd" and
"synchronousSystemCmd" or some such. The distinction is not between Unix and
"systems" in general -- it's between forking the subprocess or blocking SC
to wait for it.
hjh
--
Sent from: http://new-supercollider-mailing-lists-forums-use- these.2681727.n2.nabble.com/ SuperCollider-Users-New-Use- this-f2676391.html
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/ research/supercollider/ mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/