setCommandLineOptions do not stick after an assignment in mos scripts

[Adrian Pop]

setCommandLineOptions({"+g=MetaModelica","+d=rml,gen"});

OpenModelica.Scripting.setCFlags("-g " + getCFlags());
getErrorString();

files := {
  "../../../OMCompiler/Compiler/FrontEnd/Absyn.mo",
  "../../../OMCompiler/Compiler/Util/Error.mo",
  "../../../OMCompiler/Compiler/Util/ErrorExt.mo",
  "../../../OMCompiler/Compiler/Util/Print.mo",
  "../../../OMCompiler/Compiler/Util/StringUtil.mo",
  "../../../OMCompiler/Compiler/Util/Flags.mo",
  "../../../OMCompiler/Compiler/Global/Global.mo",
  "../../../OMCompiler/Compiler/Util/Config.mo",
  "../../../OMCompiler/Compiler/Util/Debug.mo",
  "../../../OMCompiler/Compiler/Util/List.mo",
  "../../../OMCompiler/Compiler/Util/Settings.mo",
  "../../../OMCompiler/Compiler/Util/Corba.mo",
  "../../../OMCompiler/Compiler/Util/File.mo",
  "../../../OMCompiler/Compiler/Util/Util.mo",
  "../../../OMCompiler/Compiler/Util/System.mo",
  "../../../OMCompiler/Compiler/SimCode/SimCodeUtil.mo",
  "../../../OMCompiler/Compiler/Template/AbsynDumpTpl.mo",
  "../../../OMCompiler/Compiler/FrontEnd/Dump.mo",
  "../../../OMCompiler/Compiler/Template/Tpl.mo"
};
getErrorString();

// here the flags set by setCommandLineOptions are gone!
LoadCompilerSourcesRes:= OpenModelica.Scripting.loadFiles(files);

[Adrian Pop]

Not only that but if you add setCommandLineOptions({"+g=MetaModelica","+d=rml,gen"}); before the loadFiles it will complain that it cannot find it. It seems that assignments in scripts impact the environment in a bad way.

[Martin Sjölund]

I checked this and there is nothing wrong with the command-line options being set (they are not part of the environment, but are global variables). What happens is you set MetaModelica grammar, which makes files a list<String> instead of String[:], which you cannot pass to loadFiles.