Re: GtkBuilder report

Tristan Van Berkom wrote:
> On Tue, 2007-01-23 at 13:14 -0800, Brian J. Tarricone wrote:
> [...]
>> As Tristan also mentioned for this specific case in another email, an
>> abort() in the GtkBuilder parser is ridiculously useless to the
>> developer: if there's an error in one spot in a several-hundred/thousand
>> line file, what's needed is information as to where in the file the
>> error is.  Sure, you'll notice it, but GtkBuilder's poor error-reporting
>> API design makes it that much harder to track down the actual problem.
> Just so that people dont start getting scared, I'd just like to clarify
> that this is not a restriction caused by the GtkBuilder design.
> The original write-up doesnt include contextual error reports
> for every case of a parse failure, IMO that is simply a bug,
> that doesnt mean that things need to be redisigned or anything
> to correct it, just some patchwork to be done - no big deal.

That's true: for development purposes, it's probably ok to just spit out
a "GtkBuilder parse error: file %s on line %d: expected </FOO> before
<BAR>"-type error to stderr.  So perhaps for this particular case I was
a bit overzealous, and for that, I apologise.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]