Why can not use -o and -p at the same time?

[OhYee]

I find that when I use gocc -p xxxx/xxxx -o ./analysis xxx.bnf, the package is still the default value.

It seems that because these lines.

gocc/internal/config/config.go

Lines 183 to 186 in 19e54f3

	this.outDir = getOutDir(this.outDir, this.workingDir)
	if this.outDir != this.workingDir {
	this.pkg = defaultPackage(this.outDir)
	}

If I use -o and -p together, is there any possiable problems?

I just want to put the .bnf file in a single folder.

[tsal]

I think it's possible this would break in a non-vGo / Go Modules context if both were allowed; the code generated could potentially reference packages that didn't exist.

However, since vGo is the default now, it might be better to check the environment first (for vGo), then react to the options.

It makes sense that both should be possible, but with a warning about the issues with older versions of Go.

[awalterschulze]

We are not the familiar with vGo, so a pull request to help people use gocc with vGo would be much appreciated.