On Jan 6, 2014, at 3:34 PM, Darin Adler wrote:
>
> On Jan 6, 2014, at 1:49 PM, Geoffrey Garen wrote:
>
>> FunctionParameters::FunctionParameters(ParameterNode* firstParameter,
>> unsigned size)
>> : m_size(size)
>> {
>> unsigned i = 0;
>> for (ParameterNode* parameter = firstPara
Yeah, I think there is a lot of value in keeping some Mountain Lion
coverage now that a lot of people have moved onto Mavericks on their own
machines.
Ideally, we would like to have EWS for both Mavericks and Mountain Lion
though. So perhaps we could move either release or debug bots to Mavericks
On Jan 6, 2014, at 1:49 PM, Geoffrey Garen wrote:
> FunctionParameters::FunctionParameters(ParameterNode* firstParameter,
> unsigned size)
> : m_size(size)
> {
> unsigned i = 0;
> for (ParameterNode* parameter = firstParameter; parameter; parameter =
> parameter->nextParam()) {
>
On Jan 6, 2014, at 1:49 PM, Geoffrey Garen wrote:
> auto children = elementChildren(*dummySpanAncestor);
> for (auto child = children.begin(), end = children.end(); child != end;
> ++child) {
> if (isSpanWithoutAttributesOrUnstyledStyleSpan(&*child))
> toRemove.appen
On Jan 6, 2014, at 13:49 , Geoffrey Garen
mailto:gga...@apple.com>> wrote:
Let me try to clarify with two more motivating examples:
(1) Nodes.cpp:
FunctionParameters::FunctionParameters(ParameterNode* firstParameter, unsigned
size)
: m_size(size)
{
unsigned i = 0;
for (ParameterNo
On Mon, Jan 6, 2014 at 1:16 PM, Ryosuke Niwa wrote:
> Sounds like a great idea to me.
Seconding this. nullptr also has much better compatibility with varargs than 0.
--Martin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.
06 янв. 2014 г., в 12:51, Lucas Forschler написал(а):
> The Apple Mac EWS bots are currently running 10.8.5.
> I would like to see if there is any opposition (or support) for upgrading
> them to 10.9 / Mavericks.
Mavericks bots are substantially less reliable at this point, so this will
degra
Ryosuke and I discussed this a bit over IRC. Ryosuke's main concern was
that supporting multiple document roots adds a fair amount of complexity to
NRWT. Conceptually, it's probably easier to add support to run the W3C's
new server (known as wptserve) and then maybe use it for *all* imported
tests
Let me try to clarify with two more motivating examples:
(1) Nodes.cpp:
FunctionParameters::FunctionParameters(ParameterNode* firstParameter, unsigned
size)
: m_size(size)
{
unsigned i = 0;
for (ParameterNode* parameter = firstParameter; parameter; parameter =
parameter->nextParam()
Sounds like a great idea to me.
- R. Niwa
On Mon, Jan 6, 2014 at 12:04 PM, Anders Carlsson wrote:
>
> On Jan 6, 2014, at 12:01 PM, Dan Bernstein wrote:
>
> >
> >
> > Sent from my iPad
> >
> >> On Jan 6, 2014, at 11:55 AM, Darin Adler wrote:
> >>
> >> I suggest we use nullptr, rather than of
Support here!
On Jan 6, 2014, at 12:51 PM, Lucas Forschler wrote:
> Happy near year!
>
> The Apple Mac EWS bots are currently running 10.8.5.
> I would like to see if there is any opposition (or support) for upgrading
> them to 10.9 / Mavericks.
>
> Please let me know your thoughts :)
> Lucas
Happy near year!
The Apple Mac EWS bots are currently running 10.8.5.
I would like to see if there is any opposition (or support) for upgrading them
to 10.9 / Mavericks.
Please let me know your thoughts :)
Lucas
___
webkit-dev mailing list
webkit-de
On 06/01/2014 20:23 , Ryosuke Niwa wrote:
I don't think we should do this given that the python server has been
added to W3C testing harness, and they're gonna convert all existing
tests to use that instead:
http://lists.w3.org/Archives/Public/public-test-infra/2014JanMar/.html
We should sim
On Jan 6, 2014, at 12:01 PM, Dan Bernstein wrote:
>
>
> Sent from my iPad
>
>> On Jan 6, 2014, at 11:55 AM, Darin Adler wrote:
>>
>> I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in
>> WebKit C++ sources. I don’t see any advantage to using 0 or NULL over
>> nul
Sent from my iPad
> On Jan 6, 2014, at 11:55 AM, Darin Adler wrote:
>
> I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in
> WebKit C++ sources. I don’t see any advantage to using 0 or NULL over
> nullptr, and nullptr has multiple advantages. Three obvious ones: Com
I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in
WebKit C++ sources. I don’t see any advantage to using 0 or NULL over nullptr,
and nullptr has multiple advantages. Three obvious ones: Compile time error if
accidentally passed to something expecting an integer, can be
I don't think we should do this given that the python server has been added
to W3C testing harness, and they're gonna convert all existing tests to use
that instead:
http://lists.w3.org/Archives/Public/public-test-infra/2014JanMar/.html
We should simply wait for that effort to take place and a
On Jan 6, 2014, at 10:03 AM, Alexey Proskuryakov wrote:
> As auto facilitates search-replace-don't-read refactoring
I was talking about refactoring without changing function names. I don’t
understand your example.
— Darin
___
webkit-dev mailing list
04 янв. 2014 г., в 9:51, Darin Adler написал(а):
> There are so many other things which you can’t see when reading a line of C++
> code, which I think is a good thing — part of what makes C++ a high level
> language. To create a straw man, imagine what it would be like if we had to
> say “inl
Hi,
+1 for removing the WinCE bot, it seems it isn't maintained at all.
The latest build on it was on 8th Aug, it is offline since then:
http://build.webkit.org/builders/WinCE%20Release%20%28Build%29/builds/36154
Additionally the latest build in the build.webkit.org history
was on 6 th Jun and t
20 matches
Mail list logo
