"Rozental, Gennadiy" <[EMAIL PROTECTED]> writes:
>> Maybe I should do the factorization and put it in the sandbox or
>> boost::detail...
>
> Looking forward to see that. Could you, please, let me know when you done or
> if you need my help?
Sure. I'll try to do something this week.
>>>
o
> Maybe I should do the factorization and put it in the sandbox or
> boost::detail...
Looking forward to see that. Could you, please, let me know when you done or
if you need my help?
>>
>>> optimization crop up). This is not an idiom that's been
>>> well-exercised in compiler vendors' test
"Rozental, Gennadiy" <[EMAIL PROTECTED]> writes:
>> If we are going to generalize this there should be a single
>> boost::function0 argument, and if you're going to go down this
>> path we should /definitely/ generalize it. Replicating this design
>> pattern in two separate libraries would be a b
> If we are going to generalize this there should be a single
> boost::function0 argument, and if you're going to go down this
> path we should /definitely/ generalize it. Replicating this design
> pattern in two separate libraries would be a big mistake.
I could not afford boost::function depend
"Rozental, Gennadiy" <[EMAIL PROTECTED]> writes:
>> > I could do something along following lines:
>> >
>> > #include
>> > using namespace std;
>> >
>> > void
>> > unknown_exception_handler()
>> > {
>> > try {
>> > throw;
>> > }
>> > catch( int i ) {
>> > cout << "int c
> > I could do something along following lines:
> >
> > #include
> > using namespace std;
> >
> > void
> > unknown_exception_handler()
> > {
> > try {
> > throw;
> > }
> > catch( int i ) {
> > cout << "int caught\n";
> > }
> > }
> >
> >
> > int main()
> > {
> >
"Rozental, Gennadiy" <[EMAIL PROTECTED]> writes:
>> I've encountered a problem with exceptions in boost/test:
>> Our project uses a base class for all our exceptions which
>> cannot derive
>> from std::exception.
>>
>> If such an exception is thrown, the message:
>> Exception in "...":
> I've encountered a problem with exceptions in boost/test:
> Our project uses a base class for all our exceptions which
> cannot derive
> from std::exception.
>
> If such an exception is thrown, the message:
> Exception in "...": unknown type
> is printed out, which is not very helpful
[EMAIL PROTECTED] writes:
> I've encountered a problem with exceptions in boost/test:
> Our project uses a base class for all our exceptions which cannot derive
> from std::exception.
>
> If such an exception is thrown, the message:
> Exception in "...": unknown type
> is printed out, whi
I've encountered a problem with exceptions in boost/test:
Our project uses a base class for all our exceptions which cannot derive
from std::exception.
If such an exception is thrown, the message:
Exception in "...": unknown type
is printed out, which is not very helpful in locating the p
10 matches
Mail list logo
