Summary: | Write a tools library to manipulate Visual Studio project files | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Roland Steiner <rolandsteiner> | ||||
Component: | Tools / Tests | Assignee: | Roland Steiner <rolandsteiner> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | abarth, dpranke, morrita, tony | ||||
Priority: | P3 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Bug Depends on: | 63528, 64148 | ||||||
Bug Blocks: | 61772 | ||||||
Attachments: |
|
Description
Roland Steiner
2011-06-28 05:13:39 PDT
Created attachment 100080 [details]
work-in-progress
very early draft
Comment on attachment 100080 [details] work-in-progress View in context: https://bugs.webkit.org/attachment.cgi?id=100080&action=review > Tools/Scripts/webkitpy/common/project/vcproj.py:40 > +class VCProjectException(ProjectException): > + def __init__(self, message): > + super(VCProjectException, self).__init__(message) What's the motivation for having these complicated exception class hierarchies? It's important for this code to have tests, but I presume you'll add them in later iterations of these patches. |