Commit Graph

10 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 e87d2ff210
Corrected copyright in file headers
Apparently I cannot spell my last name.
2014-06-17 01:35:24 -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 a116a4ac72 Environment expectations now permit omitting operator
Export expectations will only succeed/fail based on flag checks, whereas the
declare/set expectations will fail on value.
2014-06-13 21:29:38 -04:00
Mike Gerwitz 9045a3298b Added `exports` expectation 2014-06-13 21:29:38 -04:00
Mike Gerwitz 302977eb74 Refactored environment expectations to support grabbing flags 2014-06-13 21:29:38 -04:00
Mike Gerwitz 331a1161b2 Added `declare` as an alias for `set` expectation 2014-06-13 21:29:38 -04:00
Mike Gerwitz 7597677086 Added env var value expectation 2014-06-13 21:29:34 -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 d0e508c2f5 Extracted output expectations into separate source file 2014-05-14 00:28:08 -04:00