Hi!
On Saturday 08 January 2005 09:44, Abhay Vardhan wrote:
Is it possible to disable the lazy computation in FSA?
I don't exactly understand the intent of your question, but i guess the answer is no. However, if you mean algorithms should only return after they created the complete target automaton, then you can do at least the following with fsa. Let s be a lazy automaton. Then
StaticAutomaton *t = new StaticAutomaton(); Fsa::copy(t, s);
or even shorter (but with less functionality)
t = Fsa::staticCopy(s);
creates a copy of s and returns it after s has been traversed and copied completely. You can then access states through either the StorageAutomaton or StaticAutomaton interfaces. The only overhead compared to non-lazy execution comes from calling virtual functions (the getState method) and additionally copying states (which is necessary to keep the lazy interface clean). I never measured that overhead explicitly, but it should be in the range of 20-50% depending on the type of s.
Stephan