On Tuesday, June 28, 2011 10:29:25 steve tell wrote: > The else clause is necessary because I found that sometimes the ujtag > routines return failure without calling urj_error_set. > > Should I consider this a bug and eventually patch the core to set > an appropriate urj_error instead of working around?
in general, yes. let's take that approach.
> While chasing these down, a stronger warning or even assert would be
> helpful, but that should probably be configurable or eventually cleaned up.
in general, libraries shouldnt assert(), nor print to std{out,err}
> Just so I'm clear when testing, what is the desired logic for
> various configure usages? I'm guessing that we want:
>
> --enable-python - test for usable python, and fail configure if not found
>
> --disable-python - don't test for python, and don't build python bindings
>
> (default) - test for usable python, use it if found, else
> print warnings and continue on without python bindings
yep, that's the ticket
-mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
