In working with my date/time code I've encountered another problem with
Boost. I can reproducibly get lexical_cast to segfault. It happens when a
greg_month is lexical_cast to a string. I don't observe this behavior for
years or days, just months. The segfault can be avoided by using
lexical_cas
Stephan T. Lavavej wrote:
> In working with my date/time code I've encountered another problem with
> Boost. I can reproducibly get lexical_cast to segfault. It happens when a
> ...details omitted...
>
> Red Hat 9, gcc 3.3, Boost 1.30.0:
You should upgrade your lexical_cast.hpp to the CVS ve
At Tuesday 2003-08-05 17:36, you wrote:
In working with my date/time code I've encountered another problem with
Boost. I can reproducibly get lexical_cast to segfault. It happens when a
greg_month is lexical_cast to a string. I don't observe this behavior for
years or days, just months. The segf
Hello, I'm pretty new here, but I've extensively used boost library for
about a year.
Yesterday, I ran into a small problem, lexical_cast accepts copy instead of
(const)? reference to a source. I have a class which I would prefer to be
noncopyable and castable with laxical_cast at the same time. I'
In message <[EMAIL PROTECTED]>, Terje Slettebø
<[EMAIL PROTECTED]> writes
>>From: "Pavel Vozenilek" <[EMAIL PROTECTED]>
>
>> lexical_cast<> constructs and destroys std::stringstream
>> (including dynamic memory allocation/free.)
>> each time a conversion is done.
>>
>> Maybe specialised version of
>From: "Pavel Vozenilek" <[EMAIL PROTECTED]>
> lexical_cast<> constructs and destroys std::stringstream
> (including dynamic memory allocation/free.)
> each time a conversion is done.
>
> Maybe specialised version of lexical_cast<> can be developed
> which takes external, existing stringstream ins
lexical_cast<> constructs and destroys std::stringstream
(including dynamic memory allocation/free.)
each time a conversion is done.
Maybe specialised version of lexical_cast<> can be developed
which takes external, existing stringstream instance as
template parameter and reuses it.
Very rough i
v);
namespace foo
{
namespace bar
{
template class Formatter
{
public:
std::string getFormattedValue(const T&)
{
return boost::lexical_cast(T);
}
}
[,,,]
}
}
When I try to use
Format
Hi, I'm new to this list and I'm writing here just to suggest to you a different
implementation for lexical_cast.
Actually lexical_cast doesn't make easy to add possibilities for new casts, and
for example if I have to cast from
IpAddress class to an int it wouldn't be easy. (even casting IpAddress
In message <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] writes
>> From: Markus Werle <[EMAIL PROTECTED]>
>>
>> The feature mentioned in the subject is missing in boost.
>> (actually it throws)
>> I propose adding something simmilar to the (incomplete) stuff below.
>>
>> template
>> class lexical_strea
As already noted, new lexical_cast disables whitespace skipping, which breaks
cases like
lexical_cast(" 1");
I've just found a more serious consequence:
class Estimation_context {
public:
Estimation_context() {}
private:
int resource_count;
int eta_i
>From: "Michel André" <[EMAIL PROTECTED]>
> I get the following errors when compiling with the lexical_cast version in
> CVS on MSVC 7.0 do I have to enable wchar_t support on the command line or
> disable it via DISABLE_WIDE_CHAR_SUPPORT or whats the solution.
This problem was reported at the B
I get the following errors when compiling with the lexical_cast version in
CVS on MSVC 7.0 do I have to enable wchar_t support on the command line or
disable it via DISABLE_WIDE_CHAR_SUPPORT or whats the solution. I tried to
read up on the new lexical_cast woes with the 1.30 release but failed to
Boosters,
The update of lexical_cast caused quite a few headaches before the release
of 1.30.0. Rather than reiterating the reasons for squeezing the update into
1.30.0, I just want to thank the people involved for their efforts, and
apologize to all for the problems due to these last-minute chang
> Here is the current list:
>
> It looks to me like we should hold the lexical_cast changes until the
> next release. There are really two issues IIUC - some wide-character
> support problems and VC++ 6.0 support. While the wide-character problems
> might be possible to resolve quickly, VC++ 6.
Beman Dawes <[EMAIL PROTECTED]> writes:
> So now we'll wait until some of the other platform tests get
> updated. If their results looks as good then the update can stay in
> 1.30.0.
Without a documentation update?!?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
___
Kevlin has done an update that "incorporates the overloading fix and is
less permissive about which platforms will get wide character support."
The Win32 tests are now looking as good or better than with the old 1.29.0
version. See
http://boost.sourceforge.net/regression-logs/cs-win32-RC_1_30_0
The new lexical_cast (with the latest fixes from beman) now fails with
the darwin toolset. The error messages are at
http://boost.sourceforge.net/regression-logs/cs-Darwin-RC_1_30_0-links.html#lexical_cast_test%20darwin
Markus
___
Unsubscribe & other
> From: Dave Gomboc [mailto:[EMAIL PROTECTED]
> Yeah, I was aware that work had been done on it, but as of a couple of
> days ago CVS had no change to lexical_cast.hpp, which is what
> prompted me
> to write my original query. Could whoever did the update
> please commit it
> to CVS?
Kevlin Hen
> > Hi,
> >
> > Yes, the whitespace problem is fixed in the forthcoming version.
>
> What's "forthcoming version"? Is this forthcoming Boost release?
> Then I don't see any changes to lexical_cast.hpp at all. Or
> lexical_cast update will be committed later?
Yeah, I was aware that work had been
Kevlin Henney wrote:
>>http://lists.boost.org/MailArchives/boost/msg36221.php references an
>>improved lexical_cast. Will it or a similar improvement will be included
>>in the 1.30 release? Specifically, I'm looking for point 2: casting
>>between C-style strings and std::strings that accepts spa
> from previous thread RE: [boost] lexical_cast "Future directions"
> RE: [boost] lexical_cast "Future directions"
>
> > > A proposition has been made to fix this and other things
> > > (http://groups.yahoo.com/group/boost/files/lexical_cast_pr
from previous thread RE: [boost] lexical_cast "Future directions"
RE: [boost] lexical_cast "Future directions"
> >
> > A proposition has been made to fix this and other things
> > (http://groups.yahoo.com/group/boost/files/lexical_cast_proposition/),
I wa
ad into
std::string is a special case, as it wouldn't ordinarily allow that, as
std::string skips, and terminates reading, on whitespace. Nevertheless, it
appears that handling this special case is perceived as a useful thing, to
provide more uniform treatment of conversions. Consider:
int i=1
Hi,
On Sunday 29 December 2002 01:29, Terje Slettebø wrote:
> > there...) Anyway, the surprising result of this was that the space in
> > "Hello there" caused the interpreter.eof() check in lexical_cast to fail.
> > So if that check were not present, dest would have been assigned the
> > value "
y
nice
> from a performance perspective, but is also necessary from a functional
> perspective.
>
> Deep inside of some nested templates, I had some code that effectively did
> this due to the way the template parameters happened to play out in the
> client code:
>
> std::str
ive.
Deep inside of some nested templates, I had some code that effectively did
this due to the way the template parameters happened to play out in the
client code:
std::string source = "Hello there";
std::string dest = boost::lexical_cast< std::string >( source );
Normally, this wo
Thanks for the info.
Terje Slettebø wrote:
From: "Jasper van de Gronde" <[EMAIL PROTECTED]>
I use lexical_cast a lot, but when I tried to use it in a program that
...
in a future release, but it still isn't.
Yes, it's noticed, and it's fixed in a proposition that is scheduled to be
...
>From: "Phil Nash" <[EMAIL PROTECTED]>
> [Terje Slettebø]
> > Speaking of different character types, perhaps there could also be
> interest
> > for converting between strings of different character types, as well?
For
> > example:
> >
> > std::string str=lexical_cast(L"A wide character string");
[Terje Slettebø]
> Speaking of different character types, perhaps there could also be
interest
> for converting between strings of different character types, as well? For
> example:
>
> std::string str=lexical_cast(L"A wide character string");
> std::wstring wstr=lexical_cast("A character string");
Speaking of different character types, perhaps there could also be interest
for converting between strings of different character types, as well? For
example:
std::string str=lexical_cast(L"A wide character string");
std::wstring wstr=lexical_cast("A character string");
and the same for char->wch
>From: "Jasper van de Gronde" <[EMAIL PROTECTED]>
> I use lexical_cast a lot, but when I tried to use it in a program that
> uses Unicode I noticed it failed because it uses a standard
> stringstream. To solve my problem I simply added another #ifdef that
> checked for UNICODE and would then use w
I use lexical_cast a lot, but when I tried to use it in a program that
uses Unicode I noticed it failed because it uses a standard
stringstream. To solve my problem I simply added another #ifdef that
checked for UNICODE and would then use wstringstream, thinking it would
probably be noticed by
> "Roland" == Roland Richter <[EMAIL PROTECTED]> writes:
Roland> Dear all,
Roland> just a minor issue for the upcoming(?) lexical_cast in 1.30.0:
Roland> lexical_cast( "true" ) returns false,
Roland> since std::ios::boolalpha is not set by default.
Roland> How about chang
Dear all,
just a minor issue for the upcoming(?) lexical_cast in 1.30.0:
lexical_cast( "true" ) returns false,
since std::ios::boolalpha is not set by default.
How about changing this?
- Roland
___
Unsubscribe & other changes: http://lists.boost.o
35 matches
Mail list logo
