Exercise 48: Advanced User Input
In past games you handled the user's input by simply expecting set strings. If the user typed "run", and exactly "run", then the game worked. If they typed in similar phrases like "run fast" it would fail. What we need is a device that lets users type phrases in various ways and then convert that into something the computer understands. For example, we'd like to have all of these phrases work the same:
- open door
- open the door
- go THROUGH the door
- punch bear
- Punch The Bear in the FACE
It should be alright for a user to write something a lot like English for your game and have your game figure out what it means. To do this, we're going to write a module that does just that. This module will have a few classes that work together to handle user input and convert it into something your game can work with reliably.
A simplified version of the English language could include the following elements:
- Words separated by spaces.
- Sentences composed of the words.
- Grammar that structures the sentences into meaning.
That means the best place to start is figuring out how to get words from the user and what kinds of words those are.
Our Game Lexicon
In our game we have to create a list of allowable words called a "lexicon":
- Direction words: north, south, east, west, down, up, left, right, back
- Verbs: go, stop, kill, eat
- Stop words: the, in, of, from, at, it
- Nouns: door, bear, princess, cabinet
- Numbers: any string of 0 through 9 characters
When we get to nouns, we have a slight problem since each room could have a different set of nouns, but let's just pick this small set to work with for now and improve it later.
Breaking Up a Sentence
Once we have our lexicon we need a way to break up sentences so that we can figure out what they are. In our case, we've defined a sentence as "words separated by spaces," so we really just need to do this:
stuff = $stdin.gets.chomp words = stuff.split
That's all we'll worry about for now, but this will work really well for quite a while.
Once we know how to break up a sentence into words, we just have to go through the list of words and figure out what "type" they are. To do that we're going to use a simple array that has just two elements, and create a new Array that contains many of these. Here's an example of building one by hand:
first_word = ['verb', 'go'] second_word = ['direction', 'north'] third_word = ['direction', 'west'] sentence = [first_word, second_word, third_word]
This creates a pair [TYPE, WORD] that lets you look at the word and do things with it.
This is just an example, but that's basically the end result. You want to take raw input from the user, carve it into words with split, analyze those words to identify their type, and finally, make a sentence out of them.
Now you are ready to write your scanner. This scanner will take a string of raw input from a user and return a sentence that's composed of an array of arrays with the (TOKEN, WORD) pairings. If a word isn't part of the lexicon, then it should still return the WORD but set the TOKEN to an error token. These error tokens will tell users they messed up.
Here's where it gets fun. I'm not going to tell you how to do this. Instead I'm going to write a "unit test," and you are going to write the scanner so that the unit test works.
Exceptions and Numbers
There is one tiny thing I will help you with first, and that's converting numbers. In order to do this though, we're going to cheat and use exceptions. An exception is an error that you get from some function you may have run. What happens is your function "raises" an exception when it encounters an error, then you have to handle that exception. For example, if you type this into Ruby you get an exception:
That ArgumentError is an exception that the Integer() function threw because what you handed Integer() is not a number. The Integer()) function could have returned a value to tell you it had an error, but since it only returns integers, it'd have a hard time doing that. It can't return -1 since that's a number. Instead of trying to figure out what to return when there's an error, the Integer() function raises the ArgumentError exception and you deal with it.
You deal with an exception by using the begin and rescue keywords:
1 2 3 4 5 6 7
You put the code you want to "try" inside the begin block, and then you put the code to run for the error inside the rescue. In this case, we want to "try" to call Integer() on something that might be a number. If that has an error, then we "catch" it and return nil.
In your scanner that you write, you should use this function to test whether something is a number. You should also do it as the last thing you check for before declaring that word an error word.
A Test First Challenge
Test first is a programming tactic where you write an automated test that pretends the code works, then you write the code to make the test actually work. This method works when you can't visualize how the code is implemented, but you can imagine how you have to work with it. For example, if you know how you need to use a new class in another module, but you don't quite know how to implement that class yet, then write the test first.
You are going to take a test I give you and use it to write the code that makes it work. To do this exercise you're going to follow this procedure:
- Create one small part of the test I give you.
- Make sure it runs and fails so you know that the test is actually confirming a feature works.
- Go to your source file lexicon.rb and write the code that makes this test pass.
- Repeat until you have implemented everything in the test.
When you get to 3 it's also good to combine our other method of writing code:
- Make the "skeleton" function or class that you need.
- Write comments inside describing how that function works.
- Write the code that does what the comments describe.
- Remove any comments that just repeat the code.
This method of writing code is called "psuedo code" and works well if you don't know how to implement something, but you can describe it in your own words.
Combining the "test first" with the "psuedo code" tactics we have this simple process for programming:
- Write a bit of test that fails.
- Write the skeleton function/module/class the test needs.
- Fill the skeleton with comments in your own words explaining how it works.
- Replace the comments with code until the test passes.
In this exercise you will practice this method of working by making a test I give you run against the lexicon.rb module.
What You Should Test
Here is the test case tests/test_lexicon.rb that you should use, but don't type this in yet:
You will want to create a new project using the project skeleton just like you did in Exercise 47. Then you'll need to create this test case and the lexicon.rb file it will use. Look at the top of the test case to see how it's being required to figure out where it goes.
Next, follow the procedure I gave you and write a little bit of the test case at a time. For example, here's how I'd do it:
- Write the require at the top. Get that to work.
- Create an empty version of the first test case test_directions. Make sure that runs.
- Write the first line of the test_directions test case. Make it fail.
- Go to the lexicon.rb file, and create an empty scan function.
- Run the test, and make sure scan is at least running, even though it fails.
- Fill in psuedo code comments for how scan should work to make test_directions pass.
- Write the code that matches the comments until test_directions passes.
- Go back to test_directions and write the rest of the lines.
- Back to scan in lexicon.rb and work on it to make this new test code pass.
- Once you've done that you have your first passing test, and you move on to the next test.
As long as you keep following this procedure one little chunk at a time you can successfully turn a large problem into smaller solvable problems. It's like climbing a mountain by turning it into a bunch of little hills.
- Improve the unit test to make sure you test more of the lexicon.
- Add to the lexicon and then update the unit test.
- Make sure your scanner handles user input in any capitalization and case. Update the test to make sure this actually works.
- Find another way to convert the number.
- My solution was 37 lines long. Is yours longer? Shorter?
Common Student Questions
- What's the difference between begin-rescue and if-else?
- The begin-rescue construct is only used for handling exceptions that modules can throw. It should never be used as an alternative to if-else.
- Is there a way to keep the game running while the user is waiting to type?
- I'm assuming you want to have a monster attack users if they don't react quickly enough. It is possible, but it involves modules and techniques that are outside of this book's domain.