RESOLVED FIXED 151549
Rename JavaScriptCore builtins files to match exposed object names
https://bugs.webkit.org/show_bug.cgi?id=151549
Summary Rename JavaScriptCore builtins files to match exposed object names
Blaze Burg
Reported 2015-11-22 10:46:57 PST
As a subtask of unifying code generation for WebCore and JSC builtins, we need to get rid of differences between builtins filenames (e.g., Operations.Promise.js, Promise.prototype.js) and the name of the generated Builtin object (OperationsPromise, PromisePrototype). If we don't do this, then both build systems need special hacks to normalize the object name from the file name. It's easier to just normalize the filename.
Attachments
Proposed Fix (112.43 KB, patch)
2015-11-22 11:05 PST, Blaze Burg
no flags
Proposed Fix (18.54 KB, patch)
2015-11-22 11:08 PST, Blaze Burg
youennf: review+
youennf: commit-queue-
Blaze Burg
Comment 1 2015-11-22 11:05:59 PST
Created attachment 266057 [details] Proposed Fix
Blaze Burg
Comment 2 2015-11-22 11:08:40 PST
Created attachment 266058 [details] Proposed Fix
youenn fablet
Comment 3 2015-11-22 11:30:15 PST
Comment on attachment 266058 [details] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=266058&action=review Looks like the right direction to me. > Source/JavaScriptCore/CMakeLists.txt:1198 > ${JAVASCRIPTCORE_DIR}/builtins/GlobalObject.js This filename has no suffix. Is it ok? Should we think of renaming it also? > Source/JavaScriptCore/CMakeLists.txt:1204 > + ${JAVASCRIPTCORE_DIR}/builtins/OperationsPromise.js I would rename it to PromiseXXX.js so that it gets closer to other Promise related files. If we were to follow WebCore, it would be named PromiseInternals.js, which would relate to @internal annotation.
Blaze Burg
Comment 4 2015-11-22 16:53:52 PST
Comment on attachment 266058 [details] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=266058&action=review >> Source/JavaScriptCore/CMakeLists.txt:1198 >> ${JAVASCRIPTCORE_DIR}/builtins/GlobalObject.js > > This filename has no suffix. Is it ok? Should we think of renaming it also? I think it's okay, it's a singleton like ReflectObject and InspectorInstrumentationObject, and it can't be constructed. >> Source/JavaScriptCore/CMakeLists.txt:1204 >> + ${JAVASCRIPTCORE_DIR}/builtins/OperationsPromise.js > > I would rename it to PromiseXXX.js so that it gets closer to other Promise related files. > If we were to follow WebCore, it would be named PromiseInternals.js, which would relate to @internal annotation. OK
youenn fablet
Comment 5 2015-11-22 23:02:25 PST
Comment on attachment 266058 [details] Proposed Fix r=me
Blaze Burg
Comment 6 2015-11-23 14:10:16 PST
Note You need to log in before you can comment on or make changes to this bug.