[omniNotify] omninotify 2.0 and modulo

[Bob Gruber]

Oops, those were added to get rid of a compiler warning.  The calls to
RDI_Fatal should actually just be breaks.

292c292
<       RDI_Fatal("should not get here");
---
>       break;
327c327
<     RDI_Fatal("should not get here");
---
>     break;

I will check in a fix and also do another release. 
 
-- Bob


On Fri, 07 May 2004 10:25:45 +0200, Emmanuel Taurel <taurel at esrf.fr> wrote:
> 
> Hello everybody,
> 
> We are using omniNotify and filtering. In our filter constraints, we
> sometimes use modulo. We know that it is not part of
> the CORBA standard but it is very usefull for us. With a omniNotify 2.0
> latest release that I downloaded in October 2003, everything worked
> fine.
> It does not with the official 2.0 release !!
> 
> The problem comes from switch default cases added in the
> DRI_RVM::_widenAndResultKinds() method in the RDIRVM.cc
> file. If, in the official release 2.0, I remove the two default cases
> added between the release I downloed in October and the official 2.0
> release (line 291/292 and 326/327), everything works fine as before.
> 
> What are the consequence of removing these two switch default cases ?
> Do you continue to support "modulo" in filter constraint ?
> 
> Thank's for your answers
> 
> Emmanuel Taurel (taurel at esrf.fr)
> 
> _______________________________________________
> omninotify-list mailing list
> omninotify-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omninotify-list
>