| Summary: | nrwt multiprocessing: remove obsolete WatchableThread class | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Dirk Pranke <dpranke> | ||||
| Component: | New Bugs | Assignee: | Dirk Pranke <dpranke> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | eric, hayato, mihaip, ojan, tony | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Other | ||||||
| OS: | OS X 10.5 | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 53838 | ||||||
| Attachments: |
|
||||||
|
Description
Dirk Pranke
2011-02-04 20:08:41 PST
Created attachment 81341 [details]
remove WatchableThread
Comment on attachment 81341 [details]
remove WatchableThread
I'm not sure why inlining this class is better.
fewer lines of code, less distractions. The test code that used the WatchableThread abstraction is gone, so readers might look at this code and be puzzled by why it doesn't seem to be used anywhere. And they'd be right. If you look at the next series of patches, my goal is to move all of the real logic into single_test_runner, leaving dump_render_tree_thread.py (and worker.py) with just the communications code. Comment on attachment 81341 [details]
remove WatchableThread
Less subclassing seems better if we don't get anything from the subclassing.
Committed r77991: <http://trac.webkit.org/changeset/77991> |