Closed Bug 1218315 Opened 9 years ago Closed 9 years ago

Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16 again

Categories

(Core :: XPCOM, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla44
Tracking Status
firefox44 --- fixed

People

(Reporter: m_kato, Assigned: m_kato)

References

Details

Attachments

(7 files)

By old bug (Bug 949821), we replace with MOZ_UTF16.  But I found some landings (such as bug 1205399 etc) that still use NS_LITERAL_STRING(...).get().

Let's replace it with MOZ_UTF16() again!
Comment on attachment 8679314 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on browser

use MOZ_UTF16 instead of NS_LITERAL_STRING().get().

This is generated by same sed script of bug 949821
Attachment #8679314 - Flags: review?(nfroyd)
Comment on attachment 8679315 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on dom

Use MOZ_UTF16 instead of NS_LITERAL_STRING().get().

This is generated by same sed script of bug 949821 except to nsXULContentUtils.cpp

nsXULContentUtils.cpp should replace with it too.
Attachment #8679315 - Flags: review?(nfroyd)
Comment on attachment 8679316 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on netwerk

use MOZ_UTF16 instead of NS_LITERAL_STRING().get().

(This fix isn't generated by sed script since this uses macro)
Attachment #8679316 - Flags: review?(nfroyd)
Comment on attachment 8679318 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on rdf

Use AssignLiteral instead of Assign(NS_LIETARL_STRING(...).get()).
Attachment #8679318 - Flags: review?(nfroyd)
Comment on attachment 8679319 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on widget

use MOZ_UTF16 instead of NS_LITERAL_STRING().get().

This is generated by same sed script of bug 949821
Attachment #8679319 - Flags: review?(nfroyd)
Comment on attachment 8679321 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on xpcom

use MOZ_UTF16 instead of NS_LITERAL_STRING().get().

This is generated by same sed script of bug 949821
Attachment #8679321 - Flags: review?(nfroyd)
Attachment #8679314 - Flags: review?(nfroyd) → review+
Attachment #8679315 - Flags: review?(nfroyd) → review+
Attachment #8679316 - Flags: review?(nfroyd) → review+
Attachment #8679318 - Flags: review?(nfroyd) → review+
Attachment #8679319 - Flags: review?(nfroyd) → review+
Comment on attachment 8679321 [details] [diff] [review]
Replace NS_LITERAL_STRING(...).get() with MOZ_UTF16(...) on xpcom

Review of attachment 8679321 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks for fixing all these!
Attachment #8679321 - Flags: review?(nfroyd) → review+
This broke the Visual Studio 2015 build.
Blocks: VC14
Flags: needinfo?(m_kato)
VS2015 (not official compiler version) causes bustage due to char16_t to LPCWSTR conversion.

So Use L"" instead.
Attachment #8679990 - Flags: review?(nfroyd)
(In reply to Bas Schouten (:bas.schouten) from comment #16)
> This broke the Visual Studio 2015 build.

Sorry, I will fix soon.
Flags: needinfo?(m_kato)
Attachment #8679990 - Flags: review?(nfroyd) → review+
(In reply to Makoto Kato [:m_kato] from comment #18)
> (In reply to Bas Schouten (:bas.schouten) from comment #16)
> > This broke the Visual Studio 2015 build.
> 
> Sorry, I will fix soon.

No problem! Thanks a lot for the quick fix!
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: