[go-nuts] cgo Compiling C files housed in different directory than Go files

Hello folks. I am working on writing an Interpreter (for my own programming language) which is written in C and I want to build a Go API for my interpreter. My current directory structure is something like this ... cpank/*.c cpank/stdlib/*.c cpank/ext/*.c cpank/ext/*.h cpank/include/*.h

Re: [go-nuts] Avoid forcing my module users' to carry dependencies from code that live under the same repo just as examples/ debugging purposes.

On Fri, 2023-04-14 at 14:01 +0800, Jim Idle wrote: > You might start with this repo: > > https://github.com/golang-standards/project-layout > > This is not an 'official' standard, though it does encapsulate the > things that are standard go such as the internal directory.  > > Personally I

[go-nuts] XML to CSV utility

I required but couldn't not find an XML to CSV converter, so I wrote one. https://github.com/glycerine/xml2csv It is really bare bones/just the minimum I needed -- as it was written to process a specific dataset. Nonetheless, perhaps it will be useful to someone else as well; as the starting

Re: [go-nuts] Avoid forcing my module users' to carry dependencies from code that live under the same repo just as examples/ debugging purposes.

You might start with this repo: https://github.com/golang-standards/project-layout This is not an 'official' standard, though it does encapsulate the things that are standard go such as the internal directory. Personally I avoid its recommendation to use a directory 'pkg' to store your module