Permalink
Browse files

Words

  • Loading branch information...
1 parent 5bb7851 commit 8a9a6129274d30ccd00843855a53fb34c428d444 @msassak msassak committed Nov 13, 2010
@@ -1,2 +0,0 @@
-!SLIDE
-# BDD (or TDD, or software development, or whatever)
@@ -1,5 +1,6 @@
-!SLIDE
-# BDD with Ragel
+!SLIDE bullets incremental
+# BDD (or TDD, or software development, or whatever)
+* with Ragel
!SLIDE bullets incremental
* Get Ragel parsing _something_
@@ -14,7 +14,7 @@
# Ragel
* A tool for building parsers...
* ...by specifying state machines...
-* ...with regular expressions.
+* ...in a regular language.
!SLIDE bullets incremental
# Some people, when confronted with a problem, think "I know, I'll use regular expressions."
@@ -27,7 +27,7 @@
!SLIDE small bullets incremental
# Semantic Failure, Syntactic Confusion
* Failures with regular expressions are usually _semantic_
-* (This doesn't mean the syntax is good)
+* (This doesn't mean the syntax is that great)
* Two causes of confusion
.notes The primary source is that, well, Regexen are confusing
@@ -37,7 +37,9 @@
!SLIDE bullets
# Syntax
-* Ragel makes it easier to visualize what is happening when things go wrong
+
+* Character for character, few things produce complexity like a regular expression
+* If only there were a way to visualize what it is they create...
!SLIDE
# Thinking About Matching
@@ -47,9 +49,9 @@
!SLIDE bullets
# State Machines
-* The regex characters are the _transitions_
+* Characters in the regex are the _transitions_
* The characters of input are the _events_
-* The _states_ are generated by the compiler
+* The _states_ are determined by the compiler
!SLIDE center bullets incremental
# Example: /abc/
@@ -18,7 +18,7 @@
%%write exec;
end
end
-*
+*
!SLIDE bullets
@@@ Ruby
@@ -1,7 +1,6 @@
{ "name": "Consuming Gherkin", "sections": [
{"section":"introduction"},
{"section":"ragel_syntax"},
- {"section":"bdd"},
{"section":"bdd_with_ragel"},
{"section":"why_ragel"},
{"section":"when_ragel"},

0 comments on commit 8a9a612

Please sign in to comment.