Closed Bug 1151515 Opened 7 years ago Closed 4 years ago

Add a Components.utils.writeToStderr

Categories

(Core :: XPConnect, defect)

defect
Not set
normal

Tracking

()

RESOLVED INACTIVE
Tracking Status
firefox40 --- affected

People

(Reporter: ted, Assigned: ted)

References

(Blocks 1 open bug)

Details

Right now there's no easy way to write to stderr from chrome JS. I considered changing the implementation(s) of dump to allow sending it to stderr, but given how many implementations there are that was not appealing. I settled for adding a Components.utils.writeToStderr instead.
Assignee: nobody → ted
I'd vote for just merging the umpteen Dump implemetations, because what we have right now is nuts.
I briefly considered that but they're all pretty different. :-( window.dump is using WebIDL-generated DOM bindings, the JS shell/xpcshell ones are using raw JSAPI, and there's at least one (message manager maybe?) that I don't fully understand.
Merging would basically imply having some unified backend that takes UTF-8 or UTF-16 strings (however we produce those at the various callsites).  But yeah, I can totally understand not wanting to take this on.
I think that should be all of them, yes.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.