[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: warnings

From: Branko ╚ibej <brane_at_xbc.nu>
Date: 2001-01-25 00:59:35 CET

Ben Collins-Sussman wrote:

> So suppose libsvn_wc is working, deep down in a bunch of call frames,
> and it's trying to do 5 things. However, it wants to emit a warning
> about the 2nd action, and then move on to the 3rd, 4th, and 5th
> actions.
> Right now, we have no way to do this. If I throw a "non-fatal"
> svn_error_t, the top-most recipient can choose not to quit. But big
> deal; I've lost my call stack!
> It would be great to register some kind of "warning" function with
> libraries; this function would need to be available at all call-stack
> levels, of course. Perhaps one way to do it is to sneak it into the
> global error pool somehow?
> Thoughts?

You could store a function pointer in the error pool's userdata.

What about context? svn_error_t's can be combined during unwind after an
error, so you get information about the context for free. For getting
the warning context, you'd have to do the opposite.

Hmmm. Maybe we don't want a warning context after all. :-)

Brane ´┐Żibej
    home:   <brane_at_xbc.nu>             http://www.xbc.nu/brane/
    work:   <branko.cibej_at_hermes.si>   http://www.hermes-softlab.com/
     ACM:   <brane_at_acm.org>            http://www.acm.org/
Received on Sat Oct 21 14:36:19 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.