not a bad bug, but still made it a little difficult to debug a script --
I've noticed that in a panel data context doing:
setobs x y --panel-vars
where x is wrong (doesn't exist) yields a generic "data error". I would
have expected "x: no such thing".