Dan, your “3 3 <;._3 i. 4 4” cut example helps quite a lot. Thanks. I had found “\” very useful and had been wondering how to do the same for a frame of rank two. From Raul hypothetically speaking you might do something like what you describe in several passes -- one pass would do state transitions when they happen (obtaining a trace of these states) then you could shift the state information into the form you need it in and parse your data based on this shifted representation of state. I read about J FSM in “J for C” and then couldn’t find FSM in the dictionary. After you both replied, I found it under Vocabulary, and then discovered a lab as well. I think your descriptions give me what I need to know. Before this, I got a little stuck in my thinking. From work in another language I was trying to apply the idea of a state transition triggering an action, where the action is a piece of code, or calculation that feeds its result back into the state transition logic. Rather than get caught up in a silly amount of branching / function calls / looping, I think your suggestion of multiple passes is a good way to go. This way everything is visible, traceable, and understandable. Being descriptive doesn’t necessarily make the solution more maintainable. Also, a procedural version is not necessarily more efficient. J could be faster. I think I get the J FSM capabilities now – it’s an FSM in the pure sense. I need to work with the control logic / mapping some more, but I’m getting there.
Thanks, --Steven No virus found in this outgoing message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.16/1842 - Release Date: 10/12/2008 18:53 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
