making fgoto a no-op

Martin Pirker Martin.Pir... at
Mon Apr 21 13:39:12 UTC 2008

Dear readers....

I have


action check_data {
  fgoto *cs;     # no-op if no error occured, else stop with error


check_foo(.....) {
  if (........) {
    cs = machine_error;

I can't check the data using the Ragel machine and don't
want to place the code in the action{...} definition. So I call
out to the language side, but still want to use the Ragel
error state as feedback/abort, if errors do happen.

What are (could be) the side effects of directly manipulating
cs this way or is that approach ok?


More information about the ragel-users mailing list