Re: [PATCH] Catch errors in value_get_print_value

Daniel Jacobowitz
2007-02-09T02:26:26Z

On Fri, Feb 09, 2007 at 03:20:49PM +1300, Nick Roberts wrote:
> > > It's much quieter than a window full of error/warning messages. If
> > > there's no value available, the frontend doesn't show one. That seems
> > > logical to me but perhaps only because I'm used to it.
> >
> > Well, maybe we could use in_scope="false" and no value, and let the
> > front end decide...
>
> But the variable may be in scope and the frontend wouldn't be able to
> distinguish between this case and when the variable really was out of
> scope. Maybe another value e.g in_scope="unreadable" would work.

Maybe. I'm not going to make any changes now, and you're happy with
what we've got, so let's leave it alone for the moment - we can come
back to it.

> Isn't:
>
> if (changeable)
> {
> if (initial)
> ...
> else
> ...
> }
>
> easier to read?

In my opinion? No, not really.