[webkit-dev] node-jsc: A node.js port to the JavaScriptCore engine and iOS

2018-09-13 Thread Koby Boyango
Hi, I'm Koby Boyango, a senior researcher and developer at mce, and I've created node-jsc , an experimental port of node.js to the JavaScriptCore engine and iOS specifically. node-jsc's core component, "jscshim" (deps/jscshim)

Re: [webkit-dev] Experimental and (new) Internal feature flags

2018-09-13 Thread Dean Jackson
> On 13 Sep 2018, at 13:49, youenn fablet wrote: > > When implementing a new feature, the first thing we usually do is having an > experimental flag turned off by default. At some point, we turn on the > experimental flag for tests. When ready, the flag is turned on by default. This isn't tr

[webkit-dev] Copy WebKit Permalink for Sublime Text

2018-09-13 Thread Daniel Bates
Hi all, If you use Sublime Text, now you can generate a trac.webkit.org hyperlink to a selected code line using the Copy WebKit Permalink plugin (as of < https://trac.webkit.org/changeset/235981/>). See < https://trac.webkit.org/browser/webkit/trunk/Tools/CopyPermalink/Sublime%20Text/INSTALL> for

Re: [webkit-dev] Unified sources have broken our #include hygiene

2018-09-13 Thread Maciej Stachowiak
> On Sep 13, 2018, at 3:49 AM, Frédéric Wang wrote: > > Hi, > > I've recently found two non-trivial issues with unified builds. They are > not missing #include but instead conflicts between C++ files: > > - Two C++ files including the same header but with a #define directive > set to differen

Re: [webkit-dev] Unified sources have broken our #include hygiene

2018-09-13 Thread Michael Catanzaro
On Thu, Sep 13, 2018 at 5:49 AM, Frédéric Wang wrote: Should we allow to prevent some files to be included in unified build? You can add @no-unify in the Sources.txt. This is usually easier than rewriting code. ___ webkit-dev mailing list webkit-d

Re: [webkit-dev] Unified sources have broken our #include hygiene

2018-09-13 Thread Frédéric Wang
Hi, I've recently found two non-trivial issues with unified builds. They are not missing #include but instead conflicts between C++ files: - Two C++ files including the same header but with a #define directive set to different values [1]. - One C++ file including a header with implicit template i