ScannerRequests » History » Version 2
Version 1 (Kornelius Kalnbach, 01/29/2009 12:31 AM) → Version 2/22 (Kornelius Kalnbach, 01/29/2009 12:48 AM)
h1. Scanner Requests
Scanners are the heart of CodeRay. They split input code into tokens and classify them.
Each language has its own scanner: You can see what languages are currently supported in the "repository":http://code.licenser.net/repositories/browse/coderay/trunk/lib/coderay/scanners.
h2. Why is the CodeRay language support list so short?
CodeRay developing is a slow process, because the total number of active developers is 1 and he insists on high software quality.
Special attention is paid to the scanners: every CodeRay scanner is being tested carefully against lots of example examle source code, and also randomized and junk code to make it safe. A CodeRay scanner is not officially released unless it highlights very, very well.
h2. I need a new Scanner - What can I do?
Here's what you can do to speed up the development of a new scanner:
# Request it! File a "new ticket":http://code.licenser.net/projects/coderay/issues/new unless it already "exists":http://code.licenser.net/projects/coderay/issues?query_id=3; add a +1 or something to existing tickets to show your interest.
# Upload or link to *example code* in the ticket discussion.
#* Typical code in large quantities is very helpful, also for benchmarking.
#* But we also need the most *weird and strange code* you can find to make the scanner.
# Provide links to useful *information about the language lexic*, such as:
#* a list of reserved words (Did you know that "void" is a JavaScript keyword?)
#* rules for string and number literals (Can a double quoted string contain a newline?)
#* rules for comments and other token types (Does XYZ have a special syntax for multiline comments?)
#* a description of any unusual syntactic features (There's this weird %w() thing in Ruby...)
#* If there are different versions / implementations / dialects of this language: How do they differ?
# Give examples for *good and bad highlighters / syntax definitions* for the language (usually from editors or other libraries)
# Find *more example code*!
Also, read the next paragraph.
h2. I want to write a Scanner myself
Wow, you're brave! Writing CodeRay scanners is not an easy task because:
* You need excellent knowledge about the language you want to scan. Every language has a dark side!
* You need good knowledge of (Ruby) regular expressions.
* There's no documentation to speak of.
** But this is a wiki ^hint hint^ ;o)
But it has been done before, so go and try it!
# You should still request the scanner (as described above) and announce that you are working on a patch yourself.
# Check out the "repository":http://code.licenser.net/wiki/coderay/Repository and try the test suite (@[lang=xyz] rake test:scanners@).
# Copy a scanner of your choice as a base. You would know what language comes closest.
# Create a test case directory in @test/scanners@.
# --- Advertisement --- (No, just kidding.)
# Write your scanner!
# Also, look into @lib/coderay/scanners/_map.rb@ and @lib/coderay/helpers/file_type.rb@.
# Make a patch (scanner, test cases and other changes) and upload it to the ticket.
# Follow the following discussion.
# Prepare to be added to the THX list.
Contact me (murphy) if you have any questions.
Scanners are the heart of CodeRay. They split input code into tokens and classify them.
Each language has its own scanner: You can see what languages are currently supported in the "repository":http://code.licenser.net/repositories/browse/coderay/trunk/lib/coderay/scanners.
h2. Why is the CodeRay language support list so short?
CodeRay developing is a slow process, because the total number of active developers is 1 and he insists on high software quality.
Special attention is paid to the scanners: every CodeRay scanner is being tested carefully against lots of example examle source code, and also randomized and junk code to make it safe. A CodeRay scanner is not officially released unless it highlights very, very well.
h2. I need a new Scanner - What can I do?
Here's what you can do to speed up the development of a new scanner:
# Request it! File a "new ticket":http://code.licenser.net/projects/coderay/issues/new unless it already "exists":http://code.licenser.net/projects/coderay/issues?query_id=3; add a +1 or something to existing tickets to show your interest.
# Upload or link to *example code* in the ticket discussion.
#* Typical code in large quantities is very helpful, also for benchmarking.
#* But we also need the most *weird and strange code* you can find to make the scanner.
# Provide links to useful *information about the language lexic*, such as:
#* a list of reserved words (Did you know that "void" is a JavaScript keyword?)
#* rules for string and number literals (Can a double quoted string contain a newline?)
#* rules for comments and other token types (Does XYZ have a special syntax for multiline comments?)
#* a description of any unusual syntactic features (There's this weird %w() thing in Ruby...)
#* If there are different versions / implementations / dialects of this language: How do they differ?
# Give examples for *good and bad highlighters / syntax definitions* for the language (usually from editors or other libraries)
# Find *more example code*!
Also, read the next paragraph.
h2. I want to write a Scanner myself
Wow, you're brave! Writing CodeRay scanners is not an easy task because:
* You need excellent knowledge about the language you want to scan. Every language has a dark side!
* You need good knowledge of (Ruby) regular expressions.
* There's no documentation to speak of.
** But this is a wiki ^hint hint^ ;o)
But it has been done before, so go and try it!
# You should still request the scanner (as described above) and announce that you are working on a patch yourself.
# Check out the "repository":http://code.licenser.net/wiki/coderay/Repository and try the test suite (@[lang=xyz] rake test:scanners@).
# Copy a scanner of your choice as a base. You would know what language comes closest.
# Create a test case directory in @test/scanners@.
# --- Advertisement --- (No, just kidding.)
# Write your scanner!
# Also, look into @lib/coderay/scanners/_map.rb@ and @lib/coderay/helpers/file_type.rb@.
# Make a patch (scanner, test cases and other changes) and upload it to the ticket.
# Follow the following discussion.
# Prepare to be added to the THX list.
Contact me (murphy) if you have any questions.