Summary: | Encapsulate private properties in PerfTestRunner better | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> | ||||||
Component: | Tools / Tests | Assignee: | Ryosuke Niwa <rniwa> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | abarth, arv, eric, haraken, morrita, ojan, tkent, zoltan | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Bug Depends on: | 97743, 97852 | ||||||||
Bug Blocks: | 77037 | ||||||||
Attachments: |
|
Description
Ryosuke Niwa
2012-09-27 17:23:50 PDT
Created attachment 166315 [details]
Cleanup
Created attachment 166316 [details]
Fixed a test
Comment on attachment 166316 [details]
Fixed a test
This is fine. A less fragile approach would be to wrap the whole file in an anonymous function and at the end of the function only expose the things you really want to expose, e.g.:
window.PerfTestRunner = PerfTestRunner;
That way, everything is private by default and people don't need to move code around to enable it to use a private helper function.
(In reply to comment #3) > (From update of attachment 166316 [details]) > This is fine. A less fragile approach would be to wrap the whole file in an anonymous function and at the end of the function only expose the things you really want to expose, e.g.: Yup. I'm doing that in a follow up. I'm just trying to make the diff unreadable. *readable. Committed r130099: <http://trac.webkit.org/changeset/130099> |