Closed
Bug 520666
Opened 15 years ago
Closed 1 month ago
chromium IPC should support char, unsigned char
Categories
(Core :: IPC, defect, P5)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: joe, Unassigned)
Details
Attachments
(1 file)
1.67 KB,
patch
|
cjones
:
review+
|
Details | Diff | Splinter Review |
Currently the chromium IPC layer doesn't support serializing char or unsigned char. It should!
Reporter | ||
Updated•15 years ago
|
Attachment #404720 -
Flags: review?(jones.chris.g)
Comment on attachment 404720 [details] [diff] [review] char support >diff --git a/ipc/chromium/src/chrome/common/ipc_message_utils.h b/ipc/chromium/src/chrome/common/ipc_message_utils.h >--- a/ipc/chromium/src/chrome/common/ipc_message_utils.h >+++ b/ipc/chromium/src/chrome/common/ipc_message_utils.h >@@ -144,16 +144,52 @@ struct ParamTraits<bool> { > template <> >+struct ParamTraits<char> { [snip] >+ static void Log(const param_type& p, std::wstring* l) { >+ l->append(StringPrintf(L"%hd", p)); >+ } >+}; Minor nit: IMHO it makes more sense to log |char|s as |"'%c'"|. (And I agree that |"%hd"| makes sense for |unsigned char|.) r+ with or without that change.
Attachment #404720 -
Flags: review?(jones.chris.g) → review+
Assignee | ||
Updated•11 years ago
|
Component: DOM: Mozilla Extensions → DOM
Updated•6 years ago
|
Priority: -- → P5
Updated•6 years ago
|
Component: DOM → IPC
Updated•2 years ago
|
Severity: normal → S3
Comment 2•1 month ago
|
||
If somebody wants this, they should probably file a new bug.
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•