Overview
PyPi module | N/A | ||||||||||||||||||||
git repository | https://bitbucket.org/arrizza-public/test-golang | ||||||||||||||||||||
git command | git clone git@bitbucket.org:arrizza-public/test-golang.git | ||||||||||||||||||||
Verification Report | https://arrizza.com/web-ver/test-golang-report.html | ||||||||||||||||||||
Version Info |
|
- installation: see https://arrizza.com/setup-common.html
Summary
This is a test of the Go language. Just trying to see if it is worth the learning curve.
- run
./doit # does not build, just runs it
./do_build # builds, then runs the executable
./do_lint # invoke go lint and static check
- check if it is possible to move .mod and .work files from root directory to a sub-dir. Seems that Go has convention can make the root directory messy.
- currently the source is in:
- app
- services
- main.go
Note that most of the normal scripts available for python/ruby/c/c++ are not fully available.
- do_check: need to install python venv
- do_doc: need to see if doxygen is able to generate doc for go modules
- do_cpip_update: needed? or could be used to publish the go executable
- do_gen: needed? only used in Android/C/C++ apps
- do_post_ver: needed when UTs are implemented
- do_update: needed?
- do_ut and do_ver: currently unimplemented
Notes
- has the beginnings of a logger, see
services/logger
- other things needed to check:
- how to do efficiently do modules with instance-like attributes.
- reading/writing files
- packages for json, cfg and other file formats
- writing UTs
- try out a bg thread
- try out a socket call
- try out CLI handling