Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

  (email not shown publicly)
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Friday December 17, 2004
06:03 PM

Graphing state machines

[ #22356 ]

Yup. We're beating this state machine to death. I just wrote some preliminary code to graph the state machines. Because we now have stack tracing, I can probably trace out the actual path followed on the graph. Cool, cool, cool :)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • That looks really neat, though it's hard to follow when you don't know the criteria that pushes you from one state to the next. Such as the root_user state... I just didn't follow what happened after that state and why.

    Maybe it was your example, though. Neat stuff, though!


    • Part of the issue with any state machine is that the criteria can be confusing to an outsider if they don't know the business rules. In this case, the state machine tracks some of the dependencies for setting up Bricolage [] on PostgreSQL. The "root user" state simply means "if we have the Postgres root user, we can install. If not, check to see if we have a normal user and, if so, check to see if they can do everything necessary for the install. When I was using a bunch of nested if/else statements, it wa

  • was the code in progress at that point, or is it expected that check_permissions never leads to fail?