|
|
@ -31,8 +31,13 @@ pub struct Engine<'a, R, W> { |
|
|
|
/// For example, a start up function calls the correct "boot up" code for the engine so they only have to
|
|
|
|
/// For example, a start up function calls the correct "boot up" code for the engine so they only have to
|
|
|
|
/// worry about calling "boot up" prior to their main engine loop.
|
|
|
|
/// worry about calling "boot up" prior to their main engine loop.
|
|
|
|
///
|
|
|
|
///
|
|
|
|
|
|
|
|
///
|
|
|
|
|
|
|
|
/// TODO: THE NEXT THING - THE PARSER!
|
|
|
|
|
|
|
|
///
|
|
|
|
/// Additionally this code should have a parser. You call it with the reader supplied and it waits for a command
|
|
|
|
/// Additionally this code should have a parser. You call it with the reader supplied and it waits for a command
|
|
|
|
/// and parses it into a tuple of some kind for the user.
|
|
|
|
/// and parses it into a tuple of <token, value>. For example it would parse `setoption` into an option constant
|
|
|
|
|
|
|
|
/// and the value to set it to. This should be super generic and parsing results should just be of a type
|
|
|
|
|
|
|
|
/// ParseResult. The tuple implements ParseResult which represents a tuple of a token and value.
|
|
|
|
|
|
|
|
|
|
|
|
impl<'a, R, W> Engine<'a, R, W> |
|
|
|
impl<'a, R, W> Engine<'a, R, W> |
|
|
|
where |
|
|
|
where |
|
|
|