Bug 15910 - More cleanup and optimizations possible from ExpressionNode separation
Summary: More cleanup and optimizations possible from ExpressionNode separation
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 15885
Blocks:
  Show dependency tree / graph
 
Reported: 2007-11-08 16:51 PST by Eric Seidel (no email)
Modified: 2008-07-02 02:22 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2007-11-08 16:51:39 PST 
More cleanup and optimizations possible from ExpressionNode separation

As darin mentioned in bug 15885, now that we have ExpressionNode as a subclass of Node, it's possible to move more methods off of Node up onto ExpressionNode, as well as make some types of nodes not subclass from ExpressionNode at all (like ElementNode) and thus have a non-virtual evaluate function.  None of these are necessarily large speedups, but certainly contribute towards general cleanliness of the node tree.
Comment 1 Cameron Zwarich (cpst) 2008-07-02 02:22:45 PDT 
Thanks to SquirrelFish, this is no longer relevant.