Alexander Grund

FYI: I'm working on this and will open a new PR containing your change, rebased to develop with conflicts resolved already. That was non-trivial so I didn't want to burden...

@artyom-beilis Would you oppose that change or have any input? @salvoilmiosi You initially filed #64 and [noted](https://github.com/boostorg/locale/issues/64#issuecomment-873570559) that `as::number` would be required. So do you have an opinion on that...

I understand the motivation. I guess this is why the standard implicitly imbues the classic locale on startup and provides access to the classic locale at any point. > What...

As the errors are all of "undefined reference to " you need to link to the ICU target. In particular icudata, icui18n, icuuc, e.g. by using [`find_package(ICU ...)`](https://cmake.org/cmake/help/latest/module/FindICU.html) and the...

@artyom-beilis I think it is still a good idea to implement this: > in POSIX backend I tried to do the best I can given the tools --> The above...

> It is right and I explain why. I have to agree to @artyom-beilis here. Check this code: ``` #include #include int main() { boost::locale::generator gen; auto loc = gen("it_IT.UTF-8");...

Woops, yes: Check this: ``` auto custom_lbm = boost::locale::localization_backend_manager::global(); custom_lbm.select("posix"); boost::locale::generator gen(custom_lbm); auto loc = gen("it_IT.UTF-8"); { auto &facet = std::use_facet(loc); std::cout

> you need to use boost::locale::as::number for that kind of formatting. Not if I specifically want to use the std formatting. I.e. pretend to be some component which does not...

> Since it isn't that trivial. While working at this I now understand why. And the inconsistencies bug me, not sure how to resolve them: 1. The default formatting with...

Well what I mean: If the `CudaSetLimits` policy can only be used with the `OldAlloc` policy and the `SimpleCudaMalloc` can only be used with `Scatter` then those should be merged....