Which iomanip manipulators are 'sticky'?

前端 未结 3 1105
醉梦人生
醉梦人生 2020-11-22 16:01

I recently had a problem creating a stringstream due to the fact that I incorrectly assumed std::setw() would affect the stringstream for every ins

3条回答
  •  天涯浪人
    2020-11-22 16:59

    Important notes from the comments below:

    By Martin:

    @Chareles: Then by this requirement all manipulators are sticky. Except setw which seems to be reset after use.

    By Charles:

    Exactly! and the only reason that setw appears to behave differently is because there are requirements on formatted output operations to explicitly .width(0) the output stream.

    The following is the discussion that lead to the above conclusion:


    Looking at the code the following manipulators return an object rather than a stream:

    setiosflags
    resetiosflags
    setbase
    setfill
    setprecision
    setw
    

    This is a common technique to apply an operation to only the next object that is applied to the stream. Unfortunately this does not preclude them from being sticky. Tests indicate that all of them except setw are sticky.

    setiosflags:  Sticky
    resetiosflags:Sticky
    setbase:      Sticky
    setfill:      Sticky
    setprecision: Sticky
    

    All the other manipulators return a stream object. Thus any state information they change must be recorded in the stream object and is thus permanent (until another manipulator changes the state). Thus the following manipulators must be Sticky manipulators.

    [no]boolalpha
    [no]showbase
    [no]showpoint
    [no]showpos
    [no]skipws
    [no]unitbuf
    [no]uppercase
    
    dec/ hex/ oct
    
    fixed/ scientific
    
    internal/ left/ right
    

    These manipulators actually perform an operation on the stream itself rather than the stream object (Though technically the stream is part of the stream objects state). But I do not believe they affect any other part of the stream objects state.

    ws/ endl/ ends/ flush
    

    The conclusion is that setw seems to be the only manipulator on my version that is not sticky.

    For Charles a simple trick to affect only the next item in the chain:
    Here is an Example how an object can be used to temporaily change the state then put it back by the use of an object:

    #include 
    #include 
    
    // Private object constructed by the format object PutSquareBracket
    struct SquareBracktAroundNextItem
    {
        SquareBracktAroundNextItem(std::ostream& str)
            :m_str(str)
        {}
        std::ostream& m_str;
    };
    
    // New Format Object
    struct PutSquareBracket
    {};
    
    // Format object passed to stream.
    // All it does is return an object that can maintain state away from the
    // stream object (so that it is not STICKY)
    SquareBracktAroundNextItem operator<<(std::ostream& str,PutSquareBracket const& data)
    {
        return SquareBracktAroundNextItem(str);
    }
    
    // The Non Sticky formatting.
    // Here we temporariy set formating to fixed with a precision of 10.
    // After the next value is printed we return the stream to the original state
    // Then return the stream for normal processing.
    template
    std::ostream& operator<<(SquareBracktAroundNextItem const& bracket,T const& data)
    {
        std::ios_base::fmtflags flags               = bracket.m_str.flags();
        std::streamsize         currentPrecision    = bracket.m_str.precision();
    
        bracket.m_str << '[' << std::fixed << std::setprecision(10) << data << std::setprecision(currentPrecision) << ']';
    
        bracket.m_str.flags(flags);
    
        return bracket.m_str;
    }
    
    
    int main()
    {
    
        std::cout << 5.34 << "\n"                        // Before 
                  << PutSquareBracket() << 5.34 << "\n"  // Temp change settings.
                  << 5.34 << "\n";                       // After
    }
    
    
    > ./a.out 
    5.34
    [5.3400000000]
    5.34
    

提交回复
热议问题