One concern is that "Platform" is too generic to put in global namespace and it might conflict existing symbols from platform SDK or something. But because we already have generic names like ASSERT() and it works, this concern is just a theoretical thing.
So if it works with existing platforms, I think it's fine. -- morrita On Thu, Dec 15, 2011 at 4:02 PM, Jarred Nicholls <jar...@webkit.org> wrote: > On Thu, Dec 15, 2011 at 1:55 AM, Adam Barth <aba...@webkit.org> wrote: >> >> I was working backwards from what's going to be needed to move >> WebCore/platform out of WebCore, and it occurred to me that we'll >> probably want a separate namespace for the code once it's outside of >> WebCore, just like WTF has a separate namespace from JSC. >> >> It seems like introducing the new namespace before the move would be >> beneficial because it would help us sort out whatever layering >> violations we have today (as they'd become apparent because of the >> explicit mention of the WebCore namespace). >> >> What would be an appropriate name for the namespace? My first >> instinct is "Platform" to match the name of the new directory, but I'm >> open to suggestions. > > > I think Platform is good. When explaining it to an outsider, I refer to it > as the Client Interface or Port Interface. If Platform doesn't resonate > well with everyone then maybe something around that verbiage would fit. But > honestly I can't think of anything better than Platform. > >> >> >> Adam >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
