• Lasse Karstensen's avatar
    Add option parser, error handling and strictness. · 96c0ae47
    Lasse Karstensen authored
    This is one of those tiny jobs you start on (add --strict),
    and then it just goes downhill from there.
    
    Main changes:
    * Use optparse to parse command line arguments.
    * With --strict it aborts if a parse or format error is seen.
    * A basic test case for the parser has been added.
    
    No changes were made to the parser or output format.
    
    Adding the test case meant reordering the execution flow.
    
    Since Varnish code standard is using tabs, I've kept this to my
    best ability. Pylint is not happy about this and give the code
    a score of -4 out of 10 points. :-)
    96c0ae47
Name
Last commit
Last update
bin Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
redhat Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
Makefile.inc.phk Loading commit data...
Makefile.phk Loading commit data...
README Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
config.phk Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...