Adam Mitz

I'd start with a smaller-scoped task like adding a warning to `opendds_idl`. For that you could look at `dds_visitor::visit_structure` in `dds/idl/dds_visitor.cpp` and @iguessthislldo could provide some more details/examples of looking...

It's trivial to provide an overload of `void operator delete(void*, std::size_t)` but we would need a macro to determine which compiler versions and -std= options need it. Did you see...

> The IDL documentation supports the use of "map" Does this refer to the OMG IDL spec or somewhere else? > that corresponds to C++'s std::map object with the following...

> > Does this refer to the OMG IDL spec or somewhere else? > > In OMG's IDL spec, yes. Specifically 7.4.13.4.3.1 in IDL v4.0 or higher (formal/2016-04-02). It is...

Thanks for all the good info, @iguessthislldo and thanks for the offer to contribute, @tmayoff. My suggestion would be to start with the first major bullet point "Implement the parsing...

Wouldn't that break static builds?

Can you be more specific than "if done incorrectly"? I guess the configuration would have to be conditional on static/shared. Is there an example of this pattern somewhere else within...

If we use this, also make sure that the configure script uses `-static` with gnuace. The current version doesn't since the generated makefiles can be used for static or shared.

Is there a need for it? Will the types involved ever have an overloaded `operator&`?

Added to documentation for 3.15 and leaving this open.