Hi all,

I'd like to announce the first release of a little Go package I wrote to 
read/write PLY files: go-plyfile! You can find the source and some 
installation/usage instructions on 
GitHub: https://github.com/alexbaden/go-plyfile

go-plyfile is a Go wrapper for the PLY C Library (originally authored by 
Greg Turk -- see http://paulbourke.net/dataformats/ply/ for more). There is 
embarrassingly little Go code, but I think this package is 
relevant/interesting for a few reasons. PLY files are fairly academic, so I 
wanted to preserve the existing usage patterns as much as possible to 
encourage an easy transition to Go. I decided that wrapping the existing 
library in Go would be more fruitful than rewriting the C library entirely 
in Go. Whether this was the correct approach remains to be seen. But, I've 
used the go-plyfile package on a few other projects and haven't seen any 
issues so far. I'd appreciate some feedback from some more seasoned Go 
programmers and am curious about others experiences on making the "wrap 
existing C code vs write new Go code" decision. 

I also think a big barrier to entry for Go is the [perceived] lack of 
packages for custom file formats, etc, especially for the more 
scientific/academic file formats. For example, in my work we deal with hdf5 
files, blosc compression, PLY and VTK files, and countless other custom 
file formats (though I should note there is both an hdf5 wrapper and a 
blosc wrapper for Go).   

Finally, I haven't updated for Go 1.7 yet. I know I'm doing some 
not-so-great things with C memory access in Go and am anxious to check out 
the newly added *C.byte functionality. In the meantime, I hope this is 
useful to somebody else, and any feedback would be very much appreciated! 

Thanks,
Alex 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to