[webkit-dev] Documenting common null pointer errors

Jeremy Orlow jorlow at chromium.org
Tue Aug 11 15:13:07 PDT 2009

I would find this enormously helpful.  I also think there's less risk of it
going out of date (compared to most documentation) since the connections
between objects and their null characteristics are _very_ entrenched.

On Tue, Aug 11, 2009 at 3:03 PM, Adam Barth <abarth at webkit.org> wrote:

> In reviewing patches, I feel like I'm commonly pointing out
> DOMWindow::frame and Document::frame, etc, can be null in some
> circumstances.  Would it be useful to have a diagram of the major
> objects (Page, Frame, DOMWindow, Document, etc) somewhere on
> webkit.org that shows their relation, which links can be null, and
> which objects change / are preserved during navigation?
> If so, I'm happy to create this with my current knowledge, and
> hopefully folks with more experience will add parts that I don't know.
>  What's the best medium to make this easy to update in the future?
> SVG?  ASCII art?
> Adam
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20090811/c78c8fca/attachment.html>

More information about the webkit-dev mailing list