[go-nuts] Re: [ANN] (GUI) Qt binding which supports Windows / macOS / Linux / Android / iOS / Sailfish OS / Raspberry Pi

This looks very well done. I've not done any real programming in it but looking over the github it looks like this is well on it's way. Thank you!! i have a few programs I've been meaning to write that needed a gui, I'll be giving this a shot. On Thursday, November 10, 2016 at 3:34:36 PM

[go-nuts] Re: Version Control entire GOPATH

Have you considered gb, https://getgb.io/ ? It's purpose built for a project based workflow. On Monday, 14 November 2016 09:01:15 UTC+11, Nick Stogner wrote: > > Thanks for the replies! I would like to actually vendor the dependencies > to ensure repeatable builds (so I want to avoid

[go-nuts] Re: Version Control entire GOPATH

Thanks for the replies! I would like to actually vendor the dependencies to ensure repeatable builds (so I want to avoid submodules). In a perfect world, I would like to be able to use the go toolchain (not abandon go-get quite yet). I have been able to hack together some client-side git hooks

Re: [go-nuts] Using go to write plugins for a C host application

On Mon, Nov 14, 2016, 9:28 AM ebw wrote: > Hi! > > I tried to come up with a way to write plugins in go for a C host > application using -buildmode=c-shared. > > My first try failed, because > > go build -buildmode=c-shared > > > insisted to resolve all symbols. I thought I

Re: [go-nuts] Re: Is it a compiler bug?

I think I see the confusion here… When you have a line comment symbol “//” in go, “c” in FORTRAN, “;” in assembler, etc. you are safe. There is never confusion. When you have a block comment symbol though, “/*” and “*/” in C/C++/…/Go, “{“ and “}” in PASCAL, etc., then you have the

[go-nuts] Using go to write plugins for a C host application

Hi! I tried to come up with a way to write plugins in go for a C host application using -buildmode=c-shared. My first try failed, because go build -buildmode=c-shared insisted to resolve all symbols. I thought I could leave some symbols unresolved, so they can be later resolved, when the

Re: [go-nuts] Re: A more elegant way to store references with a slice?

Thanks all for the resources! So just to confirm, that (ref) is the only way to hold "references" to objects (and not a "reference" to a new copy) in a slice, so that I can iterate over the original objects using the slice. Correct? And In my tryref example, the issue is with the append and

[go-nuts] Re: Is it a compiler bug?

What should be wrong? It is as intuitive as it can be. Did you ever wrote a lexer/tokenizer? Am Sonntag, 13. November 2016 08:38:03 UTC+1 schrieb imd3c: > > OK, I get it. It's in the spec, I had to check it. But still, isn't it > wrong? What's the point, is it tradition or something? I checked

[go-nuts] [ANN] Go geospatial libraries: geometries, GeoJSON, WKB, KML, PostGIS, GPX, polyline

A quick announce of a few libraries for geospatial applications that are now mature and battle-tested: https://github.com/twpayne/go-geom : efficient geometry library, using a high-performance cache-friendly data representation (more info

Re: [go-nuts] Re: A more elegant way to store references with a slice?

There's also https://blog.golang.org/slices On Sun, Nov 13, 2016 at 1:50 AM, Jan Mercl <0xj...@gmail.com> wrote: > > On Sun, Nov 13, 2016 at 10:45 AM wrote: > > > Also I understand that everything is pass-by-value, but what exactly is > getting passed for tryref

[go-nuts] Re: JSON parser

I did my code, thanks all who help me. Next task, It is necessary then json string pulls out three parameters, counted and discharged into a CSV format with the columns Date, Revenue, Gold. package main import ( "database/sql" "log" _"github.com/go-sql-driver/mysql" "compress/zlib" "os"

Re: [go-nuts] Re: A more elegant way to store references with a slice?

On Sun, Nov 13, 2016 at 10:45 AM wrote: > Also I understand that everything is pass-by-value, but what exactly is getting passed for tryref that retains the id but not the slice of pointers? The answer can be found in the article linked by Volker earlier in this

[go-nuts] Re: A more elegant way to store references with a slice?

Thanks for the reply, I should've put "reference type" in quotes. The intention of the post was to get another's perspective to any better method to accomplish the example, which is to use a slice as a container of objects. Is there any other way besides how I implemented it? Also I understand