Instead of generating negative identifiers for cached resources in InspectorController and extending identifier type from 'unsigned long' to 'long long' it would be better to reuse progress tracker for the inspected page to generate those identifiers. It would guarantee that InspectorResources' ids are unique.
Created attachment 43932 [details]
Created attachment 43937 [details]
Comment on attachment 43937 [details]
I don't think we need to add methods for setting various integers - we don't even use existing ones. Can we optimize it in a way that there are only methods for signed, unsigned and floating point? That API would be easier to maintain and there will not be that much copy-paste in the code.
(In reply to comment #3)
> (From update of attachment 43937 [details])
> I don't think we need to add methods for setting various integers - we don't
> even use existing ones. Can we optimize it in a way that there are only methods
> for signed, unsigned and floating point? That API would be easier to maintain
> and there will not be that much copy-paste in the code.
We cannot reduce the number of overloaded methods without introducing lots of static_casts because if we had just double and bool there would be ambiguity for ints if we had double, bool and int there is ambiguity for long and so on.
Committing to http://svn.webkit.org/repository/webkit/trunk ...