Permalink
Browse files

port JS/CC to nodejs

  • Loading branch information...
1 parent 3368e99 commit 6471c1931d6a74b69c07099b978998c99dfb0cae @badlee committed May 17, 2011
Showing with 1 addition and 1 deletion.
  1. +1 −1 README.md
View
@@ -8,7 +8,7 @@ JS/CC is the first available parser development system for [JavaScript and ECMAS
The platform-independent software unions both: A regular expression-based [lexical analyzer](http://en.wikipedia.org/wiki/Lexer) generator matching individual tokens from the input character stream and a [LALR(1)](http://en.wikipedia.org/wiki/LALR_parser) parser generator, computing the parse tables for a given context-free grammar specification and building a stand-alone, working parser. The [context-free grammar](http://en.wikipedia.org/wiki/Context-free_grammar) fed to JS/CC is defined in a [Backus-Naur-Form-based](http://en.wikipedia.org/wiki/Backus_Naur_Form) meta language, and allows the insertion of individual semantic code to be evaluated on a rule's reduction.
-JS/CC itself has been entirely written in ECMAScript so it can be executed in many different ways: as platform-independent, browser-based JavaScript embedded on a Website, as a Windows Script Host Application, as a compiled JScript.NET executable, as a Mozilla/Rhino or Mozilla/Spidermonkey interpreted application, or a V8 shell script on Windows, *nix, Linux and Mac OSX. However, for productive execution, it is recommended to use the command-line versions. These versions are capable of assembling a complete compiler from a JS/CC parser specification, which is then stored to a .js JavaScript source file.
+JS/CC itself has been entirely written in JavaScript. These versions are capable of assembling a complete compiler from a JS/CC parser specification, which is then stored to a .js JavaScript source file.
To use JS/CC and for understanding its internals and behavior, some knowledge of context-free grammars, bottom-up parsing techniques and compiler construction theory, in general, is assumed.

0 comments on commit 6471c19

Please sign in to comment.