Closed Bug 65127 Opened 24 years ago Closed 24 years ago

Remove useless/non-error dump()s

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows ME
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: bugzilla)

Details

So, I'd like to start removing all the useless dump()s we have littered everywhere. I've already removed most of them from quite a few xpfe files. For now, I'll keep the ones that report errors or live in |catch|es; I'm mainly removing ones likes "***foopy" or "in function foo" that serve only to slow things down and fill up the console in release builds, without any real debugging gain. Anyone brave enough to give me a blank r=/sr= for this?
s/blank/blanket
Status: NEW → ASSIGNED
I actually like a few of the dumps, such as "document foo loaded successfully", and the old "webshell+ =5" (now debug-only:( ) They make it easier to figure out when an error happened relative to other things.
Those are printf()s and other C++ console output. I'm removing dump()s, which are frontend output, and usually useless.
Largely done, will remove others when touching code in the area.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
rubberstamp, unless you'd like me to check some specific places...
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.