Bug 127840 - Remove ENABLE(JAVASCRIPT_DEBUGGER) guards
Summary: Remove ENABLE(JAVASCRIPT_DEBUGGER) guards
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Csaba Osztrogonác
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 09:27 PST by Csaba Osztrogonác
Modified: 2014-01-29 11:00 PST (History)
18 users (show)

See Also:


Attachments
Patch (62.78 KB, patch)
2014-01-29 09:33 PST, Csaba Osztrogonác
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Osztrogonác 2014-01-29 09:27:52 PST
"JSC will now always support the debugger.  Hence, the #if ENABLE(JAVASCRIPT_DEBUGGER) checks can be removed."
http://trac.webkit.org/r162970 - https://bugs.webkit.org/show_bug.cgi?id=127805

Let's remove all guards.
Comment 1 Csaba Osztrogonác 2014-01-29 09:33:49 PST
Created attachment 222576 [details]
Patch
Comment 2 Mark Lam 2014-01-29 09:43:07 PST
Comment on attachment 222576 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=222576&action=review

r=me with the one issue addressed.

> Source/WebCore/inspector/InspectorInstrumentation.cpp:-1132
> -

Please revert the removal of this empty line.
Comment 3 Csaba Osztrogonác 2014-01-29 10:27:58 PST
Committed r163024: <http://trac.webkit.org/changeset/163024>
Comment 4 Csaba Osztrogonác 2014-01-29 10:30:47 PST
(In reply to comment #2)
> Please revert the removal of this empty line.
Thanks for noticing this typo, I removed it before landing.
Comment 5 Joseph Pecoraro 2014-01-29 10:35:23 PST
Hehe, I just wrote up a patch that did this yesterday and was going to send it out today. Thanks for taking care of this!
Comment 6 Joseph Pecoraro 2014-01-29 10:39:04 PST
Comment on attachment 222576 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=222576&action=review

What about:
Source/autotools/SetupWebKitFeatures.m4
WebKitLibraries/win/tools/vsprops/FeatureDefinesCairo.props
WebKitLibraries/win/tools/vsprops/FeatureDefines.props
Source/JavaScriptCore/Configurations/FeatureDefines.xcconfig
Source/WebCore/Configurations/FeatureDefines.xcconfig
Source/WebKit/mac/Configurations/FeatureDefines.xcconfig
Source/WebKit2/Configurations/FeatureDefines.xcconfig

> Source/WebCore/bindings/js/JSDOMWindowBase.cpp:109
> -#if !ENABLE(JAVASCRIPT_DEBUGGER) || !ENABLE(INSPECTOR)
> +#if !ENABLE(INSPECTOR)
>      UNUSED_PARAM(object);
>      return false;
>  #else

Down below there is a nested ENABLE(INSPECTOR) which can be removed because it is now inside of an ENABLE(INSPECTOR).

> Tools/Scripts/webkitperl/FeatureList.pm:-316
> -    { option => "javascript-debugger", desc => "Toggle JavaScript Debugger support",
> -      define => "ENABLE_JAVASCRIPT_DEBUGGER", default => 1, value => \$javascriptDebuggerSupport },

What about the definition of $javascriptDebuggerSupport?
Comment 7 Csaba Osztrogonác 2014-01-29 10:44:12 PST
(In reply to comment #5)
> Hehe, I just wrote up a patch that did this yesterday and was going to send it out today. Thanks for taking care of this!

I checked the bugzilla and haven't found bug report about it.

(In reply to comment #6)
> (From update of attachment 222576 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=222576&action=review
> 
> What about:
> Source/autotools/SetupWebKitFeatures.m4
> WebKitLibraries/win/tools/vsprops/FeatureDefinesCairo.props
> WebKitLibraries/win/tools/vsprops/FeatureDefines.props
> Source/JavaScriptCore/Configurations/FeatureDefines.xcconfig
> Source/WebCore/Configurations/FeatureDefines.xcconfig
> Source/WebKit/mac/Configurations/FeatureDefines.xcconfig
> Source/WebKit2/Configurations/FeatureDefines.xcconfig
>...

Good point, let me run one more round.
Comment 8 Joseph Pecoraro 2014-01-29 10:46:08 PST
(In reply to comment #7)
> (In reply to comment #5)
> > Hehe, I just wrote up a patch that did this yesterday and was going to send it out today. Thanks for taking care of this!
> 
> I checked the bugzilla and haven't found bug report about it.

I didn't create a bug for it. I just posted that comment saying we should remove it, and started on a patch locally. Triggered a build and had to leave early. =) Not a problem, it puts me in a good place to review this patch.
Comment 9 Csaba Osztrogonác 2014-01-29 11:00:00 PST
Here is the new bug, I hope the last one for this task :) https://bugs.webkit.org/show_bug.cgi?id=127845