Re: [go-nuts] Re: Self Built Utility package cannot access variables beyond main

No, the function does return two variables, as I take out "er" from "out, err:=" go vet report a flaw: /util.go:51:9: cannot initialize 1 variables with 2 values On Tue, Jun 10, 2025 at 10:28 AM Robert Engels wrote: > Just use VSCode with the standard Go plugin. > > On Jun 9, 2025, at 9:23 PM, K

Re: [go-nuts] Re: Self Built Utility package cannot access variables beyond main

Just use VSCode with the standard Go plugin. On Jun 9, 2025, at 9:23 PM, Kurtis Rader wrote:On Mon, Jun 9, 2025 at 7:01 PM Zhaoxun Yan wrote:Oh! Thank you Kurtis. So do you have a special Editor to inform you about the functions? My current editor cannot even tell what typ

Re: [go-nuts] Re: Self Built Utility package cannot access variables beyond main

On Mon, Jun 9, 2025 at 7:01 PM Zhaoxun Yan wrote: > Oh! Thank you Kurtis. So do you have a special Editor to inform you about > the functions? My current editor cannot even tell what type of variable a > go function would return, let alone parameter hints, etc. > I use a VIM plugin that talks to

Re: [go-nuts] Re: Self Built Utility package cannot access variables beyond main

Oh! Thank you Kurtis. So do you have a special Editor to inform you about the functions? My current editor cannot even tell what type of variable a go function would return, let alone parameter hints, etc. On Mon, Jun 9, 2025 at 1:50 PM Kurtis Rader wrote: > > > On Sun, Jun 8, 2025 at 9:35 PM Zh

Re: [go-nuts] Re: Self Built Utility package cannot access variables beyond main

On Sun, Jun 8, 2025 at 9:35 PM Zhaoxun Yan wrote: > it turned out to be an error misjudgement. The real line that caused > trouble is this: > s = er.Error()+string(out) > The error is gone after I changed it to this line : > s = fmt.Sprintf("%v %s", er, out) > The stdlib os.exec.Command()