ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> boost
boost
RE: [boost] Re: Thoughts on Format
by other posts by this author
Jan 30 2002 11:01PM messages near this date
Re: STL container of fixed capacity but variable size | RE: [boost] Boost.Format review comments - [] vs %
>  Brey, Edward D <EdwardDBrey@[...]..> writes:
> 
>  |> Do we need to put the width specifier in the placeholder at all?
>  |> Why not just put the width in a local manipulator?
> 
>  Depending on the application, the width and the precision may
>  depend on
>  the locale, and be determined by the translator. You don't
>  use the same
>  precision when formatting Italian Lire as when formatting
>  German Marks.

I think you lost the context of my remark. It was referring to widths that
are specified pragmatically. Here's the context:

>  In positional context, it becomes : %1$*2$g , meaning the first
>  argument is converted as a general float number, with width given in
>  argument number 2.

My point is that once you're in programmatic land anyway, the translators
are out of the loop and you might as well just use a local manipulator.

Of course, width specification should still be supported in the format
string for non-programmatic cases. (Plus a translator could always override
a local manipulator's width specification, if so desired.)

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved