Chris@210: = CodeRay - Trunk folder structure
Chris@210: 
Chris@210: == bench - Benchmarking system
Chris@210: 
Chris@210: All benchmarking stuff goes here.
Chris@210: 
Chris@210: Test inputs are stored in files named <code>example.<lang></code>.
Chris@210: Test outputs go to <code>bench/test.<encoder-default-file-extension></code>.
Chris@210: 
Chris@210: Run <code>bench/bench.rb</code> to get a usage description.
Chris@210: 
Chris@210: Run <code>rake bench</code> to perform an example benchmark.
Chris@210: 
Chris@210: 
Chris@210: == bin - Scripts
Chris@210: 
Chris@210: Executional files for CodeRay.
Chris@210: 
Chris@210: 
Chris@210: == demo - Demos and functional tests
Chris@210: 
Chris@210: Demonstrational scripts to show of CodeRay's features.
Chris@210: 
Chris@210: Run them as functional tests with <code>rake test:demos</code>.
Chris@210: 
Chris@210: 
Chris@210: == etc - Lots of stuff
Chris@210: 
Chris@210: Some addidtional files for CodeRay, mainly graphics and Vim scripts.
Chris@210: 
Chris@210: 
Chris@210: == gem_server - Gem output folder
Chris@210: 
Chris@210: For <code>rake gem</code>.
Chris@210: 
Chris@210: 
Chris@210: == lib - CodeRay library code
Chris@210: 
Chris@210: This is the base directory for the CodeRay library.
Chris@210: 
Chris@210: 
Chris@210: == rake_helpers - Rake helper libraries
Chris@210: 
Chris@210: Some files to enhance Rake, including the Autumnal Rdoc template and some scripts.
Chris@210: 
Chris@210: 
Chris@210: == test - Tests
Chris@210: 
Chris@210: Tests for the scanners.
Chris@210: 
Chris@210: Each language has its own subfolder and sub-suite.
Chris@210: 
Chris@210: Run with <code>rake test</code>.