FYI, check-webkit-style now supports the following via configuration variables:
(1) Suppressing certain style checks (based on category name) for particular files/folders (2) Enabling custom style checks (again based on category name) for particular files/folders (3) Skipping the style check entirely for particular files/folders Option (2), of course, requires writing additional code for the custom style checks. A consequence of (2) is that not only can ports suppress WebKit style checks -- they can also check for and enforce port-specific style rules. --Chris On Fri, Feb 19, 2010 at 7:18 AM, Evan Martin <[email protected]> wrote: > On Fri, Feb 19, 2010 at 3:30 PM, Stephan Assmus <[email protected]> wrote: >> I would like to know whether it's ok to adopt the respective platform's >> coding style in the WebKit API that a port exposes. I am working on the >> Haiku port and saw that other ports do this, but I thought I'd better ask >> before I introduce changes that may eventually be rejected. :-) > > Yes, this is ok. I'm sure you could find the discussion in the list > archives with some searches involving the words "port" and "style". > ;) > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
