Closed
Bug 78641
Opened 23 years ago
Closed 23 years ago
[console] xmlterm must not print to console in opt builds
Categories
(SeaMonkey :: UI Design, defect, P2)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla0.9.5
People
(Reporter: cls, Assigned: svn)
References
Details
(Keywords: verifyme)
Attachments
(1 file)
9.40 KB,
patch
|
Details | Diff | Splinter Review |
<formletter>It has been decreed (or requested at any rate) that our release (read non-debug) builds must not print anything to the console when the app is running. See bug 76720 for details. I have done a preliminary tree scouring and created mini-patches for each module that has bare printfs. These patches are not all inclusive as I didn't even think about xul/js output until post scour so module owners & peers will still need to scour their modules themselves as well as make sure the preliminary patches do not break anything.</formletter>
Sorry about the additional spammage but I should clear up a couple of things before everyone starts replying. 1) I'm just the messenger. Discussions outside of the specific module/patches should be discussed in the parent bug ( bug 76720). 2) I have no intention of checking in the patches as is; that's why the bugs are assigned to someone else ;). 3) The patches are the result of a far & wide-reaching grep across the entire tree. They may affect some cases that are not even used and they are far from optimal. 4) Some platforms/ports will not need the printfs shutoff as they use other mechanisms to stop the printfs. That's fine. Note it in the bug and close it as invalid(?). Depending upon the platform/port some people may still be interested in removing the overhead from the printfs.
Assignee | ||
Comment 3•23 years ago
|
||
I'll try to clean up the xmlterm code some more, but for the moment the patch looks OK to me (r=svn)
Updated•23 years ago
|
Target Milestone: --- → mozilla1.0
Comment 4•23 years ago
|
||
lets keep dribbling these [console] bugs into the tree as quick as we can, but they shouldn't hold up or block 0.9.1 so moving the target milestone to 0.9.2.
Target Milestone: mozilla1.0 → mozilla0.9.2
Is there any point to this ? Xmlterm hasn't been updated since November 2000, and doesn't work with the latest mozilla builds anyway. It's a pity, it seemed like a very nice app.
Comment 6•23 years ago
|
||
pushing out. 0.9.2 is done. (querying for this string will get you the list of the 0.9.2 bugs I moved to 0.9.3)
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Comment 7•23 years ago
|
||
moving out to 0.9.4 to get this out of the 0.9.3 radar.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Assignee | ||
Comment 9•23 years ago
|
||
Milestoned to 0.9.5 (I am in the process of restructuring the xmlterm code)
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Comment 10•23 years ago
|
||
Yay :-)
Assignee | ||
Comment 11•23 years ago
|
||
Fix checked in. Many printf's have been removed. Those that remain are ifdef'ed out of non-debug builds.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•23 years ago
|
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•