Commit Graph

5 Commits (master)

Author SHA1 Message Date
Mike Gerwitz e2f011c71d
s/::/:/g function names
The Google coding standard that used `::' was cute and all, but without a
broader framework to surround it (which I do not have time for atm), it's
too much.  `:' seems just as reasonable as a namespace delimiter.
2017-05-10 01:10:23 -04:00
Mike Gerwitz aa9044cc97 Began move to shspec::* function naming
This is motivated by Google's shell coding standards and will reduce the
odds of a naming conflict with other functions (which, of course, would
cause terribly odd and difficult-to-find bugs, in both our system and

If this seems like it creates long, overly-verbose function names with no
relief in sight---you're right. I'll have a solution for that in a bit, as a
separate project. a part of my never-ending, growing heap of projects.
2014-06-13 21:34:42 -04:00
Mike Gerwitz 61cedf54f0
.sh extension for included files
Motivated by Google's shell coding standards. This makes sense for
non-executable files.
2014-06-13 21:29:24 -04:00
Mike Gerwitz 58a3f75d05
run-spec will now set wd to spec dir
This removes sourcing complications
2014-06-09 22:39:30 -04:00
Mike Gerwitz 3d1f9d22a7
Initial concept and working tests for shspec
My original prototype was more feature-rich than this, but this formalizes
it and provides self-tests.

It is indeed odd seeing shell code that does not look like shell.
2014-05-09 00:58:06 -04:00