[omniORB] include guard on omniutilities.h

[Duncan Grisby]

On Thursday 21 November, Daniel Bell wrote:

> I've just updated from omniORB 3.0.4 to omniORB 4.0.0 and all appears to be
> going well. However, I did have some problem with compilation due to the
> include guard on include/omniORB4/omniutilities.h. The include guard is
> __UTILITIES_H__. This clashes with some one of the guards in my code. I
> can/have updated my code, but for a toolkit like omniORB, perhaps the
> include guard should be changed to something more unique like
> __OMNIUTILITIES_H__ to prevent this problem?

I've changed it in CVS. That file was originally called utilities.h,
which clashed with other things. We renamed it to omniutilities.h, but
didn't change the guard name.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --