On 16/06/2008, at 18:49, Geoffrey Garen wrote:
WebKitAvailability.h
Hmmm... Why is this in JavaScriptCore at all? It's not used there.
It's not used there *yet*. If new API is added to JavaScriptCore then
they need to be tagged with the availability macros. Rather than
having a sep
> I'm not sure where to put these:
> ExecState.cpp (runtime or vm?)
> ExecState.h
I like vm. Mostly, an ExecState represents the state of execution in
the VM. The runtime relies on the ExecState, but I wouldn't say that
the ExecState was a component of the runtime.
> completion.h
On Jun 16, 2008, at 1:53 PM, Sam Weinig wrote:
> It has always bugged me that WTF was in JavaScriptCore at all.
> Perhaps now is a good time to move it to its own project. I am not
> sure what the concerns in the past were about separating WTF from
> JavaScriptCore. Were they performance
It has always bugged me that WTF was in JavaScriptCore at all. Perhaps now
is a good time to move it to its own project. I am not sure what the
concerns in the past were about separating WTF from JavaScriptCore. Were
they performance related?
-Sam
___
w
Here is a proposal for how to rearrange the directory structure of
JavaScriptCore and move some files around. Comments welcome. First,
here's the new proposed directories:
JavaScriptCore/
api/
impl/
compiler/
docs/
os-win32/
parser/
pcre/
runtime/
5 matches
Mail list logo
