search for: test_parser

...pre> >> >> Still in the pre. >> </code> >> </pre> > > 1) Failure: > test_code_nested_pre_tags(TestParser) > [./test/helper.rb:54:in `assert_equal'' > ./test/helper.rb:11:in `assert_html_equal'' > ./test/test_parser.rb:16:in `test_code_nested_pre_tags'']: > expected: "<pre><code> Properly escaped here. &lt;pre&gt; a = > 1 &lt;/pre&gt; Still in the pre.</code></pre>" > but was: "<pre><code> Properly escaped here. &am...

...wn. I propose then to make official this new formalism. Here can be find the grammar of the formalism : http://opensource.mgeups.com/projects/nut-config/grammar.od I made a parser for the new formalism and put sample files and a test program on my branch (JD-NewConf branch, in test directory). The test_parser take a file name as parameter, parse it and then print the tree corresponding to the file. Please feel free to play with it and to torture it. I think there is no bug (I tested it with valgrind), but if you see one, please tell me. I put a Makefile in the test directory and modified Makefile.in, so...

> $ rake test > /usr/local/bin/ruby -Ilib:test "/usr/local/lib/ruby/gems/1.8/gems/ > rake-0.7.3/lib/rake/rake_test_loader.rb" "test/test_formatters.rb" > "test/test_parser.rb" > Loaded suite /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/ > rake_test_loader > Started > ...................................................................... > ...................................................................... > .........................