Basically, the N actions will be able to be customized (that is, you'll be
able to add your own levels).
What you say, about throwing an exception, also will be possible, since
you'll be able to set a "handler" for each level of assertion.
So, for instance, for assertions with level Debug (default)
Beman Dawes wrote:
> > ... various backup suggestions
>
> SourceForge already makes the entire Boost CVS tarball available every
> night, and several Boosters download it daily.
Oh, good. There is no such thing as too much backup.
> (At least I hope they do - I have no way of telling if they a
A 2-3% timing difference probably isn't reliably repeatable in real code.
My timing tests were interleaved as I swapped in various algorithms and
recompiled and the time differences were consistent. I gave ranges not
averages to give a feel for the "experimental error".
I'm not sure, though, if
I just made a mistake with the MPL and got this error message:
c:/boost/boost/python/init.hpp:246: warning:
`typename boost::mpl::iterator_range<
boost::mpl::begin<
boost::python::detail::type_list<
T0, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T1
David Abrahams wrote:
>
> the following fails to compile. Should it?
>
> --
>
> #include
> #include
>
> namespace mpl = boost::mpl;
> typedef mpl::vector v10;
> typedef mpl::push_back::type v11;
>
Contrary to what the docs say, no. Please see
http://groups.yahoo.com/group/Boost-Users
> Right!
> However, I think this would be a great feature (and a good name -
> BOOST_VERIFY) - to allow the same behaviour as ASSERT in release as well.
> What do you think? Do you think of a better name?
how about just VERIFY() :-)
-Thorsten
___
Uns
To Victor:
You still haven't replied to the posting below. Am I to take this to mean
that you have no answer, i.e. you were wrong but won't admit it? Or do you
tend to offend people for no reason, and not care about it?
If I don't hear anything from you, I'll assume both, because I have no
reason
On Thursday, May 8, 2003, at 10:12 AM, Kresimir Fresl wrote:
Matthias Troyer wrote:
That's a good point. I have prepared a version separate from
functional.hpp and posted it on our web server:
http://www.comp-phys.org/software/function_objects/
Shouldn't the default type of the result of `logic
Gennaro Prota wrote:
> Just that Borland won't warn on BOOST_INVARIANT(false). Admittedly
> not a big one :-)
This warning can be configured away simply by purposely accessing a non-constant
variable or calling an inline function:
inline bool force_non_constant() { return true; }
if (force_non_
Somewhere in this thread I lost track of this -- but just how
do out<> and in<> differ from ref<> and cref<>?
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Thursday, May 8, 2003, at 11:07 America/Denver, Beman Dawes wrote:
At 11:11 AM 5/8/2003, Darin Adler wrote:
>On Thursday, May 8, 2003, at 07:04 AM, Beman Dawes wrote:
>
>> A 2-3% timing difference probably isn't reliably repeatable in real
>> code.
>>
>> How code and data happens to land in har
On Thursday, May 8, 2003, at 10:07 AM, Beman Dawes wrote:
I notice the examples you give are JavaScript.
Sorry I wasn't clear. The examples I gave were speed improvements to a
JavaScript interpreter, written in C++.
For example, some C++ compilers are a lot more aggressive about
inlining than o
At 11:11 AM 5/8/2003, Darin Adler wrote:
>On Thursday, May 8, 2003, at 07:04 AM, Beman Dawes wrote:
>
>> A 2-3% timing difference probably isn't reliably repeatable in real
>> code.
>>
>> How code and data happens to land in hardware caches can easily swamp
>> out such a small difference. The vers
the following fails to compile. Should it?
--
#include
#include
namespace mpl = boost::mpl;
typedef mpl::vector v10;
typedef mpl::push_back::type v11;
--
foo.cpp: In instantiation of `boost::mpl::push_back':
foo.cpp:9: base
`boost::mpl::push_back_traits >::algorithm'
has
John Torjo wrote:
Sorry for the late reply...
Don't worry about it - I've been kinda busy lately
The library is in great shape!!!
Thanks :-)
I love the idea behind format_traits! formatob as well!
Why did you opt for the .space() function? I think it could have been
included in the .format func
--- Daniel Frey <[EMAIL PROTECTED]> wrote:
> Gennaro Prota wrote:
> > On Thu, 8 May 2003 15:06:02 +0300, "John Torjo" <[EMAIL PROTECTED]>
> > wrote:
> >
> >>Unfortunately, we can't use the do-while(0) idiom, since we don't know when
> >>while(0) will be ;-)
> >>
> >
> > Oops, no. That's not the p
Gennaro Prota wrote:
On Thu, 8 May 2003 15:06:02 +0300, "John Torjo" <[EMAIL PROTECTED]>
wrote:
Unfortunately, we can't use the do-while(0) idiom, since we don't know when
while(0) will be ;-)
Oops, no. That's not the problem. The problem is that I read Daniel's
reply out of context and too absent-
> > If VERIFY is used in MFC to mean an assert even in release mode then
that
> is
> > probably the best name.
> In MFC it doesn't have that meaning though. It means that the expression
> passed to VERIFY will get evaluated in the release build but the result of
> this expression will not get che
On Thu, 8 May 2003 15:06:02 +0300, "John Torjo" <[EMAIL PROTECTED]>
wrote:
>Unfortunately, we can't use the do-while(0) idiom, since we don't know when
>while(0) will be ;-)
>
>Example:
>BOOST_ASSERT(i != j)(i)(j);
>
>or
>
>BOOST_ASSERT(i > 1000)(i);
Oops, no. That's not the problem. The problem
My experience tuning our java VM is similar, and it runs on a lot of
different CPUs. Still, there is reason to be suspicious of very small
changes, which might be repeatable for our benchmark set, yet have no
real meaning for normal use. And there is reason to be careful not to
waste time pursuin
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
On Thursday, May 8, 2003, at 07:04 AM, Beman Dawes wrote:
A 2-3% timing difference probably isn't reliably repeatable in real
code.
How code and data happens to land in hardware caches can easily swamp
out such a small difference. The version-to-version or step-to-step
differences in CPU's, me
At 07:28 PM 5/7/2003, Darren Cook wrote:
>Well it was a real-world example and I only applied it to one of the
>classes. 2-3% speed boost for only three extra lines of code (header
>include, new, delete) is worth having.
A 2-3% timing difference probably isn't reliably repeatable in real code.
Ho
Roland Richter said:
> Dear all,
>
> I'm new with Boost.Threads; I've just worked with
> Java Threads so far.
>
> One feature of the Java language is the "synchronized"
> keyword - to make variables, methods, code blocks etc.
> thread-safe. So, when I first came into the situation
> th
> ... various backup suggestions
SourceForge already makes the entire Boost CVS tarball available every
night, and several Boosters download it daily.
(At least I hope they do - I have no way of telling if they are still
running their cron jobs.)
That is supposed to protect us from total failu
> If VERIFY is used in MFC to mean an assert even in release mode then that
is
> probably the best name.
In MFC it doesn't have that meaning though. It means that the expression
passed to VERIFY will get evaluated in the release build but the result of
this expression will not get checked in releas
Gennaro Prota wrote:
> >I think this is a bit more complicated that it should be. Why don't just
> >create boost-wide commit emails mailing list?
>
> Off-hand _this one_ seems more complicated, because it involves more
> people than necessary and forces to keep the diffs (though just for,
> say, a
Roland Richter wrote:
It seems to be easy to synchronize variables - see the
very minimalistic draft below. But what about synchronized
class methods etc.?
Using the scoped_lock on a mutex (like you have done in the example),
will work for the entire method. The lock isn't freed until the me
Christopher Currie wrote:
> While in theory I agree with Aleksey, I tried David's suggestion of
> inhibiting in-class static constant initialization. This single change
> eliminatated all but one of the remaining problems I've had compiling
> the tests for type_traits (there's still an assertion ha
On Thu, 08 May 2003 15:30:05 +0400, Vladimir Prus <[EMAIL PROTECTED]>
wrote:
>Gennaro Prota wrote:
>
>> I drop an idea: suppose that when there's a new
>> commit the CVS informs, via e-mail, the penultimate people that had
>> done a commit. This way I (the generic developer) can do the
>> followin
>
> That's right. But if this will ever get into boost maybe we'll better
> use the classical do-while(0). Borland warns on if(false), and
> assert(false) is quite common, for instance, in the default case of
> switch statements. BOOST_INVARIANT(false) could be used similarly
> (Though, depending o
> #include
>
> struct Keeper
> {
> Keeper(int) {}
> operator bool() { return false; }
>
> template< class type>
> void log( const type & val, const char * str)
> { std::clog << str << "=" << val; }
> };
>
> template< class type>
> struct log_me_t
> {
> log_me_t( const v
On Mon, 5 May 2003 20:12:13 -0700, "Paul Mensonides"
<[EMAIL PROTECTED]> wrote:
>Daniel Frey wrote:
>> Paul Mensonides wrote:
>>
>>> #define BOOST_INVARIANT(expr) \
>>> if (!(expr)) \
>>
>> One possible enhancment:
>>
>>if( expr ); else
>>
>> It prevents problems when the macro is
> > Under win32, my assert method uses
> >
> > if (IsDebuggerPresent())
> > {
> > DebugBreak();// ammounts to int 3 on intel
> > }
>
> Maybe that is the 4th alternative I couldn't think of earlier :-). I also
> thought of one more: emailling the system administrator. Useful on
servers.
Ind
> Darren Cook wrote:
> >
> > In my own assert library I added options for logging, but in the end
> > never used that and always had it throw an exception. This is nice for
> > two reasons:
> > 1. MFC debugger catches it and allows me to go back up the call stack
> > to where the assert happene
> >>BOOST_ASSERT(some_lenghty_function())(???)
> >
> > 2. BOOST_ASSERT( some_lengthy_function() > 10)
some_lengthy_function());
> > Indeed, is kind of lengthy, but this is life :-(
> > The point is that I could provide the v_ macro as well - it would not be
too
> > complicated. What do others th
Gennaro Prota wrote:
> Thanks Aleksey. I was particularly interested to stlport.hpp
> (incidentally: though that doesn't affect the good functioning of the
> file, the space between # and endif:
>
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/boost/config/stdl
ib/stlport.hpp.diff?r1=
John Maddock wrote:
> That would be a big help - I have about a dozen changes to the regex-4
> branch that have been lost - and I haven't even begun to figure these out
> yet :-(
Just in case if you missed it - we have an option of getting access to the
2003-05-07 backup:
> Additionally:
> If you
> > 4. In case an assertion has failed, two actions will occur:
> > - first, the assertion will be logged
> > - second, a message will be show to the user, and the user can choose
from
> > multiple actions, like Ignore, Retry, Abort, etc.
> >
> > These are SEPARATE actions, and are both customiza
Gennaro Prota wrote:
> I drop an idea: suppose that when there's a new
> commit the CVS informs, via e-mail, the penultimate people that had
> done a commit. This way I (the generic developer) can do the
> following: before doing any commit check out the whole repository (in
> order to have the ne
Under win32, my assert method uses
if (IsDebuggerPresent())
{
DebugBreak();// ammounts to int 3 on intel
}
Maybe that is the 4th alternative I couldn't think of earlier :-). I also
thought of one more: emailling the system administrator. Useful on servers.
which I find better than the de
Dear all,
I'm new with Boost.Threads; I've just worked with
Java Threads so far.
One feature of the Java language is the "synchronized"
keyword - to make variables, methods, code blocks etc.
thread-safe. So, when I first came into the situation
that I needed threads in C++ as well, I thought
On Thu, 8 May 2003 05:20:11 -0500, Aleksey Gurtovoy
<[EMAIL PROTECTED]> wrote:
>
>I just restored the lost revisions for these three headers:
>
>boost/config/platform/win32.hpp
>boost/config/stdlib/stlport.hpp
>boost/filesystem/convenience.hpp
>
Thanks Aleksey. I was particularly i
Darren Cook wrote:
>
> Anywhere in Boost is fine by me; currently it is in boost::detail and
> not in the documentation.
Given enough pressure... and documentation... and tests... ;-)
> OK. How about a template parameter to specify page size? We could use
> the platform and the class size to gues
> I just restored the lost revisions for these three headers:
>
> boost/config/platform/win32.hpp
> boost/config/stdlib/stlport.hpp
> boost/filesystem/convenience.hpp
>
> and, comparing what is probably the most recent "before-the-disk-crash"
CVS
> snapshot to the current CVS state, it
I just restored the lost revisions for these three headers:
boost/config/platform/win32.hpp
boost/config/stdlib/stlport.hpp
boost/filesystem/convenience.hpp
and, comparing what is probably the most recent "before-the-disk-crash" CVS
snapshot to the current CVS state, it seems that
Alexander Nasonov wrote:
> I agree that a->move(10, 10) is clearer then move()(a, 10, 10). One big
> plus of it is ability to overload move member-function: a->move(Point(10,
> 10)). You can't do that with move operation:
> move()(a, 10, 10);
> move()(a, Point(10, 10)); // error
> You have to i
On Wed, 07 May 2003 15:54:14 -0400, Beman Dawes <[EMAIL PROTECTED]>
wrote:
>At 03:30 PM 5/7/2003, Douglas Gregor wrote:
>
> >Would you mind adding these directories and files back? My checkout is
>too
> >old to be of use, so we really need those that have the newest files to
> >check them back in
Darren Cook wrote:
In my own assert library I added options for logging, but in the end
never used that and always had it throw an exception. This is nice for
two reasons:
1. MFC debugger catches it and allows me to go back up the call stack
to where the assert happened. (I'm still struggling
BOOST_ASSERT(some_lenghty_function())(???)
2. BOOST_ASSERT( some_lengthy_function() > 10) ( some_lengthy_function());
Indeed, is kind of lengthy, but this is life :-(
The point is that I could provide the v_ macro as well - it would not be too
complicated. What do others think?
I wondered about thi
4. In case an assertion has failed, two actions will occur:
- first, the assertion will be logged
- second, a message will be show to the user, and the user can choose from
multiple actions, like Ignore, Retry, Abort, etc.
These are SEPARATE actions, and are both customizable.
Customization can hap
51 matches
Mail list logo
