search for: dignost

...on > on > > the success path. > > But they are always created, even if it as error the caller wants to > ignore. For example, you will always create a "file foo.o in bar.a is > not a bitcode" message (or copy sufficient information for that to be > created). With a dignostic handler no copying is needed, since the > call happens in the context where the error is found. It is easy to > see us in a position where a lot of context is copied because some > client somewhere might want it. > > So I am worried we are coding for the hypothetical and adding &gt...

Dear List: the CODA and BOA packages for the analysis of MCMC output yield different results on two dignostic test of convergence: 1) Geweke's convergence diagnostic; 2) Heidelberger and Welch's convergence diagnostic. Does that imply that the CODA and BOA packages implement different ``flavors'' of the same test? I paste below an example. Geweke's test cbind(coda.gwk,boa.gwk)...

Hi Rafael, > But they are always created, even if it as error the caller wants to > ignore. For example, you will always create a "file foo.o in bar.a is > not a bitcode" message (or copy sufficient information for that to be > created). With a dignostic handler no copying is needed, since the > call happens in the context where the error is found. It is easy to > see us in a position where a lot of context is copied because some > client somewhere might want it. I'm not saying that this system would replace diagnostic handlers in g...

> > I don't think these are really independent. Whether or not you need to emit > > a diagnostic depends on whether a caller can handle the corresponding error, > > which isn't something you know at the point where the error is raised. > But you do in the diag handler. For example, if you are trying to open > multiple files, some of which are bitcode, you know to