@@ -75,21 +75,21 @@ void TestMessageFormat2::testFormatterAPI() {
7575 // if there's a syntax error
7676 UnicodeString pattern = " {{}" ;
7777 MessageFormatter::Builder mfBuilder (errorCode);
78- mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_BEST_EFFORT); // This shouldn't matter, since there's a syntax error
78+ mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_BEST_EFFORT); // This shouldn't matter, since there's a syntax error
7979 mfBuilder.setPattern (pattern, parseError, errorCode);
8080 MessageFormatter mf = mfBuilder.build (errorCode);
8181 U_ASSERT (errorCode == U_MF_SYNTAX_ERROR);
8282
8383/*
8484 Parsing is done when setPattern() is called,
85- so setErrorHandlingBehavior(MessageFormatter::Builder:: U_MF_STRICT) or setSuppressErrors must be called
85+ so setErrorHandlingBehavior(MessageFormatter::U_MF_STRICT) or setSuppressErrors must be called
8686 _before_ setPattern() to get the right behavior,
8787 and if either method is called after setting a pattern,
8888 setPattern() has to be called again.
8989*/
9090 // Should get the same behavior with strict errors
9191 errorCode.reset ();
92- mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_STRICT);
92+ mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_STRICT);
9393 // Force re-parsing, as above comment
9494 mfBuilder.setPattern (pattern, parseError, errorCode);
9595 mf = mfBuilder.build (errorCode);
@@ -99,7 +99,7 @@ void TestMessageFormat2::testFormatterAPI() {
9999 pattern = " {{{$x}}}" ;
100100 errorCode.reset ();
101101 // Check that a pattern with a resolution error gives fallback output
102- mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_BEST_EFFORT);
102+ mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_BEST_EFFORT);
103103 mfBuilder.setPattern (pattern, parseError, errorCode);
104104 mf = mfBuilder.build (errorCode);
105105 U_ASSERT (U_SUCCESS (errorCode));
@@ -108,7 +108,7 @@ void TestMessageFormat2::testFormatterAPI() {
108108 U_ASSERT (result == " {$x}" );
109109
110110 // Check that we do get an error with strict errors
111- mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_STRICT);
111+ mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_STRICT);
112112 mf = mfBuilder.build (errorCode);
113113 U_ASSERT (U_SUCCESS (errorCode));
114114 result = mf.formatToString (MessageArguments (), errorCode);
@@ -118,15 +118,15 @@ void TestMessageFormat2::testFormatterAPI() {
118118 errorCode.reset ();
119119 pattern = " hello" ;
120120 mfBuilder.setPattern (pattern, parseError, errorCode);
121- mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_BEST_EFFORT);
121+ mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_BEST_EFFORT);
122122 mf = mfBuilder.build (errorCode);
123123 U_ASSERT (U_SUCCESS (errorCode));
124124 result = mf.formatToString (MessageArguments (), errorCode);
125125 U_ASSERT (U_SUCCESS (errorCode));
126126 U_ASSERT (result == " hello" );
127127
128128 // Check that behavior is the same with strict errors
129- mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_STRICT);
129+ mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_STRICT);
130130 mf = mfBuilder.build (errorCode);
131131 U_ASSERT (U_SUCCESS (errorCode));
132132 result = mf.formatToString (MessageArguments (), errorCode);
@@ -286,7 +286,7 @@ void TestMessageFormat2::testAPICustomFunctions() {
286286 MessageFormatter::Builder mfBuilder (errorCode);
287287 UnicodeString result;
288288 // This fails, because we did not provide a function registry:
289- MessageFormatter mf = mfBuilder.setErrorHandlingBehavior (MessageFormatter::Builder:: U_MF_STRICT)
289+ MessageFormatter mf = mfBuilder.setErrorHandlingBehavior (MessageFormatter::U_MF_STRICT)
290290 .setPattern (" Hello {$name :person formality=informal}" ,
291291 parseError, errorCode)
292292 .setLocale (locale)
0 commit comments