Commit Graph

8 Commits (7338fb4748a7d1fb937c9825d5ff3617a85422f9)

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 2845e64b74
Output hexdump comparisons on expect failure
* src/spec.sh (fail): Output xxd hexdump of std{in,out}.
  (bail): Output to stderr.
2017-04-19 01:59:15 -04:00
Mike Gerwitz a368e809a3
Support binary comparisons by `expect'
* src/spec.sh
  (__spec_result): Remove variable.
  (__spec_outfile): Add variable.
  (expect): Write stdout to temporary file rather than storing in variable,
    which strips trailing whitespace and does not handle null bytes.
  (shspec::__handle-to): Use `$__spec_outpath'.
  Update copyright years.

* test/test-spec: Add tests for trailing whitespace and binary comparison.
2017-04-19 01:57:42 -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 961ebf0255 {_sstack-=>shspec::stack::_} 2014-06-13 21:34:42 -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
others').

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. ...as a part of my never-ending, growing heap of projects.
2014-06-13 21:34:42 -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