• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

NFA Metastate Handling

0 posts in this topic



All references to "thread" within this post refer to co-operatively multitasked artificial threads managed within the state machine, that execute "concurrently".


I grew frustrated with porting my NFA regex engine from C, and ditched it in favor of rewriting it entirely. The problem that I have is that in this state machine, there are two types of states: "active" states that match characters and determines whether or not the thread advances to the next state, or dies, and "passive" states (metastates) that don't affect whether or not a thread passes, but have side effects on the thread's execution. An example of a passive state is the "split" state: this state indicates a fork in the execution path with no condition, and the current thread takes one path while spawning another thread that takes the other. Another example is the pair of passive states that indicate the start and end of a looping construct; they both hold a pointer to the looping context that points to the beginning and ending, and has information on the bounds for repetition. When a thread hits the loop start state, it initializes its loop counter for that instance and reads the looping context, and automatically proceeds to the next state. Depending on the loop, it may also spawn a thread that skips the loop if zero iterations are an allowed possibility. When a thread hits the loop finish state, depending on the loop it may spawn a thread to loop again, starting just after the loop start state, and if it is within the bounds for repetition, the thread is permitted to pass on to the states after the loop while the other thread tries looping again, otherwise it dies.


The main problem is, passive states can occur anywhere, and be in any quantity. A passive state may be anywhere, including the first or last states in the machine's execution path. More than one passive state may be attached consecutively. The idea is to process all of the passive states in between each active state; execution is driven by each character of the input string being evaluated one at a time, with all threads moving in lock-step. So, for every character of the input, one active state, along with any number of passive states in between, will be processed to determine whether the thread passes or fails at that step. I'm hoping to ditch my old, hackish method of checking for some state types at the beginning of the step, some after a thread passes its active state, and some after adding the thread back to the thread list. I currently have three "actions": the thread passes, and execution moves to the next thread; the thread fails and is removed from the thread pool; or the thread is "retried", and evaluated again during the same step. For the most part, "retrying" is used when a thread hits a passive state and advances to the next state, but hasn't hit an active state yet, and thus needs to continue executing.


I'd like to handle all state types in one place, but they seem to come at different times in execution, and not all threads have the same amount of passive states between active states due to the different execution paths. I can't come up with a clean solution that would handle all three of these cases:

The first state is a passive "split" state, forking threads to try to match 'a' and 'b' at the same time. This requires checking for passive states at the same time as active states, since it is possible to encounter either one as the first state.



The first state is an active state matching 'a', the second is a passive loop start state, the third is an active state matching 'b', and the fourth is a loop finish state. Here, after either active state, there are passive states that need to be handled.



The first and last states are passive loop states. At the end of the string, the matcher part of the engine seeks out the threads that are at the "match" state, indicating that they successfully matched the pattern. However, if "b" is the input, there is one step. This means that in order to find an active state on the first and only step, and end at the match state, one needs to check for passive states before _and_ after the active state, since there is one step. Perhaps a final flushing step with no character input? It smells hackish, and will likely lead to code duplication.


Does anyone know of a good way to handle this situation?


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0