dq8081 2015-05-07 13:39
浏览 170
已采纳

将.go文件作为附加参数传递给`go run`

For quick hacking, I prefer to use go run prog.go ... instead of building the executable first. However, the program I am working on should take another go-file as an argument. As a consequence, go run and the compiled binary behave differently:

go run prog.go foo.go

will try to execute both go-files, whereas

go build prog.go && ./prog foo.go

will correctly take my file as input (the intended behaviour). Now I can pass additional args like this go run ... -- foo.go, but then because of the -- the position of the file differs in os.Args between the go run prog.go -- foo.go and the ./prog foo.go. Any easy solution? I'd like to avoid having full flag-processing. Should I just give up and stick to the compiled version?

  • 写回答

2条回答 默认 最新

  • dtoka218420 2015-05-07 14:33
    关注

    It's not possible. Here's the source for the command:

    for i < len(args) && strings.HasSuffix(args[i], ".go") {
        i++
    }
    files, cmdArgs := args[:i], args[i:]
    

    You can use go install instead of go build. That will put your executable in your $GOPATH/bin folder (I don't like having the binary in the same folder because sometimes I accidentally add it to git). But it's really not much different.

    Another option you might want to consider is rerun. It will automatically recompile and run your code whenever you change a file:

    rerun path/to/your/project foo.go
    
    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)

报告相同问题?

悬赏问题

  • ¥15 使用ue5插件narrative时如何切换关卡也保存叙事任务记录
  • ¥20 软件测试决策法疑问求解答
  • ¥15 win11 23H2删除推荐的项目,支持注册表等
  • ¥15 matlab 用yalmip搭建模型,cplex求解,线性化处理的方法
  • ¥15 qt6.6.3 基于百度云的语音识别 不会改
  • ¥15 关于#目标检测#的问题:大概就是类似后台自动检测某下架商品的库存,在他监测到该商品上架并且可以购买的瞬间点击立即购买下单
  • ¥15 神经网络怎么把隐含层变量融合到损失函数中?
  • ¥15 lingo18勾选global solver求解使用的算法
  • ¥15 全部备份安卓app数据包括密码,可以复制到另一手机上运行
  • ¥20 测距传感器数据手册i2c