Robert Ramey wrote:
>>> iv) requirement to have separt save/load code for serialization
>>> functions
>
>>I though about it just recently, and stubmled upon the issue of
>>const-correctness. Probably, separate save/load is OK, since I don't know
>>any good alternative solution.
>
> I was always
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
In article <[EMAIL PROTECTED]>, Vladimir Prus
<[EMAIL PROTECTED]> writes
>
>The principle of least astonishment can be applied in a different way. We
>all know that lexical cast uses streams, and
>
>stringstream ss(" 1 ");
>int i;
>ss >> i;
>cout << i << "\n";
>
>certainly works. I
"Vesa Karvonen" <[EMAIL PROTECTED]> writes:
> Vesa Karvonen:
> I have now implemented a subset of the language I described in my
> previous post. It turns out that my extrapolation is not completely
> bogus.
Great!
> It is definitely possible to get reasonable performance from
> the interprete
Joel de Guzman <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> David B. Held wrote:
> > "Fernando Cacciola" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]
> >> [...]
> >> I think I like this enhanced version.
> >> 'max_size_type_that_fit_in_padding'
> >> must better
Kevlin Henney wrote:
> In article <[EMAIL PROTECTED]>, Vladimir Prus
> <[EMAIL PROTECTED]> writes
>
> >The principle of least astonishment can be applied in a different way. We
> >all know that lexical cast uses streams, and
> >
> >stringstream ss(" 1 ");
> >int i;
> >ss >> i;
> >co
Vladimir Prus wrote:
> Does those "alternate streams" belong to filesystem library at all?
> For one thing, the ':' symbols is not allowed anywhere except for root name.
> For another thing, on all systems but NTFS, "bar.baz.blip:blat" would be
> considered as having "blip:blat" extension, and ma
Fernando Cacciola wrote:
> padding 100%, but which will be quite easy to use is this:
>
> template
> struct aligned_storage
> {
> void const* address() const ;
> void* address();
>
> // If tag_t fits in the padding, it is allocated there,
> // else it is allocated separately (but i
Jason House wrote:
> Vladimir Prus wrote:
> > Does those "alternate streams" belong to filesystem library at all?
> > For one thing, the ':' symbols is not allowed anywhere except for root
> > name. For another thing, on all systems but NTFS, "bar.baz.blip:blat"
> > would be considered as having "b
I'm still having problems with using the new iterator adaptors, when trying to create
input iterator with the help of 'iterator_facade'. The complete code
is attached. The problems are with 'deference' method.
1. iterator_facade insists on having const 'deference', while it seems that input
it
Christopher Currie wrote:
>Hello,
>
>Attached is a quick patch to microsec_time_clock.hpp, which in CVS fails to compile
>under
>cygwin due to a missing header file. Please let me know if there’s something that I’m
>doing wrong here. I found the bug trying to build the socket library in boost-sa
I have quite a bunch of tests which use test execution monitor and look like
this
int test_main(int ac, char* av[])
{
test_a();
test_b();
}
and so on. There's another method, in which there's "init_unit_test_suite"
method, which returns a property initialized test_suit
At 09:15 AM 4/21/2003, Vladimir Prus wrote:
>Jason House wrote:
>> Vladimir Prus wrote:
>> > Does those "alternate streams" belong to filesystem library at all?
>> > For one thing, the ':' symbols is not allowed anywhere except for
root
>> > name. For another thing, on all systems but NTFS, "bar.b
At 10:37 PM 4/20/2003, Edward Diener wrote:
>Beman Dawes wrote:
>> The idea is that rather than directory iteration returning iterators
>> for
>> all path entries, it would only return those which passed a predicate
>> which was driven by the pattern. For some uses, the pattern might
>> more flexi
[I've cc'd this to the -lib reflector because a post-meeting mailing
will propose these adaptors for the TR and issues of possible defects
in the standard are addressed here]
Vladimir Prus <[EMAIL PROTECTED]> writes:
> I'm still having problems with using the new iterator adaptors, when
> trying
15 matches
Mail list logo
