Closed Bug 69873 Opened 25 years ago Closed 24 years ago

get rid of |nsAutoCString|

Categories

(Core :: XPCOM, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: scc, Assigned: dbaron)

References

()

Details

Attachments

(2 files)

This class (which _looks_ like |nsCAutoString|) has never really been part of the string hierarchy. It acts much like |nsXPIDLCString|. We need to get rid of it. It mostly appears in relation with |nsFileSpec| another class that is supposed to go away.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
Blocks: 28221
Blocks: 53065
No longer blocks: 28221
No longer blocks: 53065
Depends on: 53065
Blocks: 28221
Target Milestone: mozilla0.9.1 → mozilla0.9
secondary api issue
Blocks: 73009
No longer blocks: 28221
Target Milestone: mozilla0.9 → mozilla1.1
re-targeting milestones, starting from a clean slate
Target Milestone: mozilla1.1 → ---
Taking. Patch coming, once it compiles. (BTW, it looks more like NS_LossyConvertUCS2toASCII than anything else, except that it heap-allocates.)
Assignee: scc → dbaron
Status: ASSIGNED → NEW
Since attaching the patch I fixed the indentation of what I added in nsFileSpecMac.cpp to the proper combination of tabs and spaces that works at any tab setting and I changed the ToNewCString in nsInstall.cpp to an nsCRT::strdup.
Comment on attachment 53119 [details] [diff] [review] working patch r=jag
Attachment #53119 - Flags: review+
Checked in 2001-10-11 19:57/58 PDT.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
could this patch cause bug 108350?
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: