Closed
Bug 654743
Opened 14 years ago
Closed 14 years ago
Cleanup debug statments in the editor
Categories
(MailNews Core :: Composition, defect)
MailNews Core
Composition
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 5.0b1
People
(Reporter: Usul, Assigned: Usul)
Details
Attachments
(1 file, 2 obsolete files)
10.73 KB,
patch
|
Usul
:
review+
|
Details | Diff | Splinter Review |
Some file have DEBUG_username in them.
Remove that debug code to clean up the tree.
Attachment #530046 -
Flags: review?(dbienvenu)
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #530046 -
Attachment is obsolete: true
Attachment #530046 -
Flags: review?(dbienvenu)
Attachment #530626 -
Flags: review?(dbienvenu)
Comment 2•14 years ago
|
||
Comment on attachment 530626 [details] [diff] [review]
More complete cleanups with NS_DEBUGs too
No need for the braces here, anymore:
if (nsMsgIsLocalFile(url.get()))
{
mCompFieldLocalAttachments++;
-#if defined(DEBUG_ducarroz)
- printf("Counting LOCAL attachment %d: %s\n", mCompFieldLocalAttachments, url.get());
-#endif
}
else // This is a remote URL...
{
mCompFieldRemoteAttachments++;
-#if defined(DEBUG_ducarroz)
- printf("Counting REMOTE attachment %d: %s\n", mCompFieldRemoteAttachments, url.get());
-#endif
}
/**** I think this should just be replaced with
DoFcc();
Because the returns aren't needed, nor is the return code.
nsresult retCode = DoFcc();
if (NS_FAILED(retCode))
{
-#ifdef NS_DEBUG
- printf("\nDoDeliveryExitProcessing(): DoFcc() call Failed!\n");
-#endif
return;
}
else
{
// Either we started the copy...cleanup happens later...or cleanup will
// be take care of by a listener...
return;
}
r=me, with those comments addressed.
Attachment #530626 -
Flags: review?(dbienvenu) → review+
Assignee | ||
Comment 3•14 years ago
|
||
Patch ready for checking
Attachment #530626 -
Attachment is obsolete: true
Attachment #530812 -
Flags: review+
Assignee | ||
Updated•14 years ago
|
Keywords: checkin-needed
Comment 4•14 years ago
|
||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•