roblem.
It is no fun writing a virus for Linux, becase all 12 users would be
infected immediately, and there it ends. If you write for Windows, you
can infect a hundred million.
Bo Persson
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
re they
will to if Notus turns out it be successful. .-)
Bo Persson
[EMAIL PROTECTED]
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
tually producing a bool value.
Adding == 0 or != 0 is often all it takes.
Bo Persson
[EMAIL PROTECTED]
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
be unavailable as there is an
explicit
specialisation further down this file that is designed to
treat an
unsigned short as a character.
If you wish to read or write unsigned shorts to wchar_t
streams, you should
consider making wchar_t a native
"Alisdair Meredith" <[EMAIL PROTECTED]> skrev i
meddelandet news:[EMAIL PROTECTED]
> Bo Persson wrote:
>
> > Instead of dropping elements when the buffer is full, we might
also
> > consider waiting or throwing a failure.
>
> "The one true circul
t; pushing to the back and popping from the front.
Could make it too general!
A buffer where you add elements at one end and remove them from the
other can have interesting multi-threading semantics if you have
exactly one producer and one c
the value and not
update a parameter:
y = year_of_first_marriage();
Having a function lying about its purpose should be caught at its
definition, not at each call of the function:
void will_never_change_any_parameters_honest(int& x) { x = 7; }
is easy to catch early. :-)
Bo Persson
[E
tever you change doesn't screw up VC++ 7.0.
>
Disabling this warning would hardly affect 7.0, as it is just an indication
that 7.1 properly usues argument-dependent lookup, which 7.0 does not
(except for operators...).
A lot of the fail
