Re: [icu-support] UnicodeString::toUTF8String, why BOM?

[Gregorio L. <g.l...@gm...>]

1) Fair. I don't use those calls THAT much but to be on the safe side, I think I'll just construct it on app startup or when the display language changes.

2) Awesome, thanks.


P.S. Happy new year to all who helped me here.


Gregorio Litenstein Goldzweig
Médico Cirujano


• Fono: +56 9 96343643
• E-Mail: g.l...@gm...

On 30 Dec 2024 at 0:43 -0300, Fredrik Roubert <ro...@go...>, wrote:
> On Sat, Dec 28, 2024 at 2:42 AM Gregorio Litenstein
> <g.l...@gm...> wrote:
>
> > 1) Are instances of icu::Locale expensive to construct?
>
> Kind of, maybe, maybe not. They're definitely not trivial to
> construct, but whether that's an issue for your use-case is something
> that you only can find out by doing measurements.
>
> > 2) Do I need to worry about cleaning them up? and if so, how?
>
> In terms of memory management there's nothing strange about them, they
> behave just like any normal C++ object, once constructed you can think
> of them and handle them just like you would do with std::string
> objects.
>
> --
> Fredrik Roubert
> ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/89643f51-5a27-4714-bd3e-7481df3c7955%40Spark.