Article 8
No: If we see -- then that forces the current set of arguments to end, but if we decide to end the arguments when we see foo then we don't look ahead to see if a -- is coming.
View ArticleArticle 7
According the runghc's help message: runghc [-f GHC-PATH | --] [GHC-ARGS] [--] FILE ARG Shouldn't runghc -- -main-is foo -- bar.hs suffice (without the --ghc-arg flag) ?
View Articlestatus changed; resolution set
status changed from new to closedresolution set to fixed OK, this is now done in 6.8 and HEAD, but you need to escape the argument to -main-is so runghc doesn't think it's the module to load: runghs...
View ArticleArticle 4
Strange, I thought the whole point of :main was that it ran whatever -main-is was set to. I must have been dreaming that. I'm not sure we need set arg-style, rather I'd like to see the argument...
View ArticleArticle 3
:main also always runs main, regardless of any -main-is flag, currently. Also, it parses arguments itself, so we would have to build strings in such a way that it would parse them correctly. Also, ghc...
View ArticleArticle 1
Other unix programs' example -e behavior (well, at least in the GNU versions): #sed: run the two expressions in sequence (for each line) echo 123 | sed -e 's/1/2/g' -e 's/2/4/g' 443 #grep: any -e...
View ArticleArticle 0
I've seen things like ghc -e 'let foo = bar in do baz foo putStrLn "ha ha" ' | some other shell command ... how about allowing multiple -e expr arguments, which are done in sequence? At present it...
View Article
