Mirror of forum.nim-lang.org

1778 :: Nimscript exec() on Windows

• Tayku (orginal) [2015-11-08T02:42:25+01:00] view original

  Trying out Nimscript for standalone scripts, I was a bit fiddling around. Unfortunately already a simple exec does not work as expected. I cannot give command line arguments to the command I want to execute, nor can I execute a command without options.

  mode = ScriptMode.Verbose
  
  exec("ping")
  exec("ping www.google.com")
  exec("ping", "")
  exec("ping", "www.google.com")
  Run

  Only the calls 3 and 4 are executed, but in both cases without the command line options (so it prints the ping manual).

  From a look in the source, in calls 1 and 2 the proc rawExec is executed – which simply does nothing. In calls 3 and 4, the proc staticExec is called, which executes the command but the arguments are not propagated. The only way working is echo(staticExec("ping www.google.com")), but that seems as a hack.

---

• Tayku (orginal) [2015-11-08T02:43:09+01:00] view original

  As it seems the forum will prevent "long" postings, my additional questions:

  Does exec not work on Windows systems? Why are two different exec procs used for the same command (with and without arguments)?

---

• Varriount (orginal) [2015-11-08T07:34:21+01:00] view original

  @Tayku: It's likely a bug - could you post the compiler source code in question? Nimscript is a relatively new feature, so it still needs some work.

---

• Araq (orginal) [2015-11-08T10:44:01+01:00] view original

  The windows installer misses an important file for Nimscript to work, that's why you see bugs like these. The bug has been fixed, but I'm still collecting bugfixes for 0.12.2.

---

• Tayku (orginal) [2015-11-08T12:31:31+01:00] view original

  Thank you for the information (though it would have saved me some time if this was published or added to the release notes). I will wait patiently for the next bugfix release. :)

---