On Wed, Jul 7, 2010 at 9:58 AM, Sasha Khapyorsky <sas...@voltaire.com> wrote: > On 10:00 Tue 06 Jul , Roland Dreier wrote: >> >> Seems that anyone who cared could already easily write a tiny shim in C >> and then write the rest of their plugin in C++. Or are there deeper >> issues than names of methods? > > I think that it is likely deeper. For instance if C++ stuff will use > OpenSM structures, functions, include files, etc.. So this will > automatically will add some limitations for using normal C in OpenSM > core code.
Perhaps but are these significant ? AFAIK we been living with them since the early days of OpenSM. > I highly suspect that all those "requirements" are resulted by using C++ > in some third party's *proprietary* plugs. It's not just "some third party's "proprietary" plugs." C++ use has been in open source in OpenFabrics for quite some time now in ibutils. Also, since "extern C" has been in the header files since the early days, there can be many out of tree uses in C++ code. > Which is fine in general, but > completely unrelated to OpenSM development - I don't think that we should > care. IMHO if users want to use C++ with OpenSM related development then we should and need to care. -- Hal > Sasha > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
