Bug 15910
| Summary: | More cleanup and optimizations possible from ExpressionNode separation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | darin |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| Bug Depends on: | 15885 | ||
| Bug Blocks: | |||
Eric Seidel (no email)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Cameron Zwarich (cpst)
Thanks to SquirrelFish, this is no longer relevant.