Different applications and environments want and need different behavior out of assert() failures. Under Win32, for example, if a DirectDraw application owns the frame buffer, it may not be possible to put up an "assertion failed" message box. Will D provide an application-overridable report-assertion-failed hook?

-RB

Assert fails throw an exception, which you can catch and deal with as required.


"Russell Borogove" <kaleja@estarcion.com> wrote in message news:3BF595AC.482BF097@estarcion.com...
> Different applications and environments want and need different behavior out of assert() failures. Under Win32, for example, if a DirectDraw application owns the frame buffer, it may not be possible to put up an "assertion failed" message box. Will D provide an application-overridable report-assertion-failed hook?
>
> -RB

Walter wrote:
> 
> Assert fails throw an exception, which you can catch and deal with as required.

Ah, of course -- that's even in the spec, but my tiny little brain swapped it out.

-RB

"Russell Borogove" <kaleja@estarcion.com> wrote in message news:3BF6D873.278C2BEC@estarcion.com...
>
>
> Walter wrote:
> >
> > Assert fails throw an exception, which you can catch and deal with as required.
>
> Ah, of course -- that's even in the spec, but my tiny little brain swapped it out.

That's ok, I find myself forgetting what's in the spec some times, too!