Re: Re: [Fastcgipp-users] Re: converting data to string

[ninti]

In general I support the idea of keeping things as simple and as standard as 
possible. The reason I've been attracted to C++ from PHP5 is the prospect of 
better speed and performance. I'd hate to see fastcgi++ end up as bloated with 
helper functions as Zend Framework, for example.  
 
Now that I know about <sstream>, my particular issue is solved. There is 
probably 
not a great need for a string version of REMOTE_ADDR, I just like to include it 
in emails sent from a website. That and maybe logging are the only use cases I 
can think of right now and they're both relatively peripheral. 
 
Mike 
 
 
On Wed 06/01/10  6:54 AM , Eddie Carle address@hidden sent: 
> On Mon, 2010-01-04 at 08:24 -0700, Axel von Bertoldi wrote: 
> > Maybe the Address class could benefit from a 
> getString() method? 
> Yeah, I am torn on this one. Standard C++ calls for the use of streams 
> to handle turning custom data types into a human readable format. A 
> getString() function, albeit convenient, is only of any use to 
> std::string. What if one is using custom string types. At least they 
> have the option of deriving basic_ostream to utilize the same 
> conversionfunctions. 
> -- 
> Eddie Carle 
>  
>  
>  
>  
>  
>