[Webkit-unassigned] [Bug 58016] [EFL] Memory cache API

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 13 07:16:43 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=58016





--- Comment #11 from Grzegorz <g.czajkowski at samsung.com>  2011-04-13 07:16:43 PST ---
(In reply to comment #10)
> (In reply to comment #9)
> > > I'm saying that the only reason this pointer could be NULL is if there was an out-of-memory condition. In that scenario, WebCore would failed to load before this function could ever be called.
> > > 
> > Yes, I agree with you. But there is possibility to get the cache for instance in ewk function and to set the pointer on NULL, right? I know it's stupid but we can't exclude that case.
> 
> Wooww... how would that function do that? We are returning a pointer not a pointer to pointer... Even if the stupid ewk function called delete on that pointer, subsequent calls to MemoryCache::memoryCache() would not return NULL.
Ok, I won't say anything about pointers from now ;)
I will remove checking NULL.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list