Closed Bug 39226 Opened 24 years ago Closed 24 years ago

Remove obuffer size guessing from mimetpla.cpp

Categories

(MailNews Core :: MIME, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: BenB, Assigned: BenB)

References

Details

Code cleanup.

Currently, there're come calculations abotu how large the out buffer could grow
after txt->html transformation. This is a bit bogus, because you just can't
know. We don't even need it, because we use nsString to hold the result anyway,
which grows automatically as needed.

My only concern is, that I don't understand libmime well. Rich, does
obj->obuffer have any side-effect or is it inititalized, used and discarded in
MimeInlineTextPlain_parse_line, i.e. can I savely remove it and just do
something like |tmp = output.ToNewCString(); MimeObject_write(obj, tmp,
output.Length(), PR_TRUE); Recycle(tmp);|?
Depends on: 31906
Target Milestone: --- → M18
Status: NEW → ASSIGNED
Target Milestone: M18 → M17
Fix checked in by rhp.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
QA Contact: lchiang → stephend
http://lxr.mozilla.org/seamonkey/search?string=obuffer

obuffer exists in other portions of mime, but not in this file.

Marking Verified FIXED.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.