Re: [PATCH] Catch errors in value_get_print_value

Nick Roberts
2007-02-09T02:21:07Z

> > 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.

Re your patch:

if (initial && changeable)
...
else if (changeable)
...

Isn't:

if (changeable)
{
if (initial)
...
else
...
}

easier to read?