On Mon, Dec 17, 2007 at 10:56:05PM +0100, Marc Lehmann <[EMAIL PROTECTED]> wrote: > > string, preferably via an argument to the configure M4 macro > > All public symbols are already prefixed with ev_ and there are no public > symbols except as required by the API. If you need to rename some symbols > it is easy enough to do so yourself with a simple #define.
In the light of the following discussion, let me elaborate this more, to avoid the obvious question: unlike libevent, which exports almost all of its functions, including the internal ones (e.g. http://ue.tst.eu/95cc821336a4aab78072252c587acb05.txt), libev ONLY exports truely public symbols (see here, http://ue.tst.eu/eaffbcc456fe160ff44f462e8cf9694a.txt, this is the *full* list of exported symbols for the current release). You can get rid of the event_ ones if you don't use the libevent emulation, too. That means that there is no need to rename symbols internally, as internal symbols are not visible. If you feel the need to rename external symbols you can easily do so yourself (this isn't, in general, required when embedding libev, though). In any case that means that openmpi already suffers from any such probelms and seems to cope well, too. It certainly will become much easier with libev. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] -=====/_/_//_/\_,_/ /_/\_\ _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
