State Machines - advantages and disadvantages

Hi,

while all types of coding (assuming correct code) should result in same behaviour, there might be some difference in resource usage. But I'm not pretty sure myself currently..

Assuming the written directives are translated to hardware more or less directly, the coding style with both, state transisitions and outputs in the same process might end up with the output signals being decodede not only by the current state but including the input signals as well. If there are two processes - one including states and state transisitions and a second to define the output signals only depending on the actual state this might be a more resource efficient style (while it's definitely far less readable as you need two tables to identify the transition and the output conditions...).

Has anyone tried to implement a more or less small FSM in these two styles to compare the resource usage in e.g. Cyclone devices which are more register than LUT based...?