Remove char*s from mozTXTToHTMLConv

VERIFIED WONTFIX

Status

P3
normal
VERIFIED WONTFIX
19 years ago
11 years ago

People

(Reporter: BenB, Assigned: BenB)

Tracking

({perf, regression})

Trunk
perf, regression

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

19 years ago
For bug #21203 / bug #26915, mscott replaced nsStrings with |PRUnichar*|s.
See bug #21203 for an explanation, why I don't think. this is a good idea.

Chris Waterson wrote, that I can go back to nsString, if that is no perf
decrease in comparison to the current state. I think, this is possible.

I even argue, that this is already true, because mscott's changes decreased
performance for western human language by factor 2, and I think, this is the
vastly most important case (much more important than source code, where my
version was weak). However, I will see, if I can increase performance for the
other cases (source code etc.) as well.
(Assignee)

Comment 1

19 years ago
No milestone goal for now, but propably M15.

> See bug #21203 for an explanation, why I don't think. this is a good idea.

Summary: Stability, Unmaintainable for me
Status: NEW → ASSIGNED
Keywords: perf, regression
(Assignee)

Comment 2

19 years ago
I thought about it: The recent checkin was too much.

I really see no reason for checking in mscott's patch: It decreases stability,
performance and maintainability. But I'm willing to revisit this, if somebody
shows me a rational explanation.

Currently, I don't have a desire to fix this bug (in order to make maintaining
the class possible again for me). WONTFIX.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WONTFIX
(Assignee)

Comment 3

19 years ago
With the new string implementations, we propably don't need char*s. If I
understood it right, there'll be an implementation, which can handle usage of
|Right()| very well.

Use the last (already optimized) mozTXTToHTMLConv implementation using nsStrings
(can be found at bug 26915), convert it to the new string API, optimize it with
the new string implementations and redo all recent changes to the current tree
version of mozTXTToHTMLConv.
Summary: Remove string pointers from mozTXTToHTMLConv → Remove char*s from mozTXTToHTMLConv

Comment 4

18 years ago
Any more comments on this, or can we verify this as a WONTFIX?
(Assignee)

Comment 5

18 years ago
> we verify this as a WONTFIX?

Please leave that to somebody from the Mailnews team.

Updated

16 years ago
QA Contact: lchiang → stephend
verified
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.