omniidl and C++ include guard naming

I previously posted this on the user mailing but didn't get much input, so 
sorry for duplication:

  Is there any way to control the names that omniidl uses when generating 
  include guards in C++ headers? If I'm dealing with two sets of IDL, both 
  of which have a (for instance) Util.idl, the generated header files will 
  both use the same macro definition for the include guard. Is there any 
  way I can tell the C++ backend to use some sort of pre/suffix to 
  differentiate these names? The problem, of course, is that these macros 
  collide if some translation unit includes both of these generated 
  headers.

I was told that there is no support for controlling the guard names. As 
such, I propose that we/I/someone add this functionality. I'd be happy to 
look into doing this, but I could use some pointers on where to start.

I think this is important (really, critical) functionality, and I can't 
imagine that it will be too hard to add. Thanks for any help on this.

--
Austin Bingham

Signal & Information Sciences Laboratory
Applied Research Laboratories, University of Texas at Austin
10000 Burnet Rd., Austin, TX 78758

email:  [email protected]
cell:   (512) 799-2444
office: (512) 835-3832