How about a clearer policy of using assert()'s?

I'm thinking that error()'s should be reserved for "real" runtime errors.


>        if (!tap_is_state_stable(path[num_states - 1]))
>        {
>                LOG_ERROR("BUG: TAP path doesn't finish in a stable state");
> -               exit(-1);
> +               jtag_set_error(ERROR_JTAG_NOT_STABLE_STATE);
> +               return;
>        }


The above should be an assert().


-- 
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to