On Thu, Jan 31, 2013 at 2:57 PM, Dirk Pranke <dpra...@chromium.org> wrote:
> On Thu, Jan 31, 2013 at 2:52 PM, Alexey Proskuryakov <a...@apple.com> wrote: > > > > 31.01.2013, в 14:45, Dirk Pranke <dpra...@chromium.org> написал(а): > > > >>>> One thing to keep an eye on with WEBCORE_EXPORT is that it can > increase > >>>> the number of exports for each port, because it would export symbols > that > >>>> are only needed for other ports. > >>> > >> > >> I'm not sure I understand the concern here. Is the idea that some > >> ports might build WebCore as a DLL (and need exports) and others > >> wouldn't? Or the idea that the API that is needed to be exported might > >> vary from port to port in such a way that too many symbols for WebCore > >> might be exported on some ports? > > > > The latter. > > > > I suspect that it's somewhat less of an issue for JavaScriptCore, > because its exports are mostly used from cross-platform code. > > > > I see. Some concrete examples would be helpful here (to me, at least). > What components and ports are we talking about, and what sorts of > symbols? > FWIW, there are quite few symbols exported from EditorMac.mm although of them are if-def PLATFORM(MAC)'ed in .h anyway. - R. Niwa
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev