Re: An even better implementation of 22.2.6.2.2 ??

[Paolo Carlini <pcarlini at unitus dot it>]

>More or less.  (I hate calling widen over and over again, and doing
>all kinds of memory allocations during I/O, but that's a whole 'nother
>issue.)  We need to think about whether the fill characters go before
>or after the space, because the standard is entirely unclear on the
>point.  Generally, they probably shouldn't go between the space and
>the currency symbol, because the space is there to separate the
>currency symbol from other stuff.  Thus,
>
>  1000****** DMK
>  ITL ******1000

> This is purely a QOI matter, but once we choose we're probably
> stuck with it.

I see.
It would be ok with you if for the time being we bring to conformance the code
with the patch I have just posted and then, in a second round, we refine it for
the various QoI patterns?

(I'm afraid the space case will become quite a bit longer, since we have to
determine if the current index i is before or after the index corresponding to
symbol (only if showbase, of course, otherwise, which is a sensible default?)

Thanks, Paolo.