Hi Holger, Do you have a clear idea what could be done easier/better/safer with C++ in this case? I general I'm a big fan of C++ because it's easier to write safe/better code, but in this exact case we're already deep into C style and I'm not sure we could change that with a reasonable amount of effort. If you have concrete proposals, please send them for discussion. Otherwise I agree that we should change the code to be pure C, even though I don't like C. On Mon, Jul 29, 2013 at 3:33 PM, Holger Hans Peter Freyther <hfreyther@sysmocom.de> wrote:
Dear Ivan, all,
I started to do work on the PCU and didn't compile C++ for a long time. I was surprised how long it takes to compile the code. From my point of view we are taking the hit of g++ without really using any of the features that C++ vould provide (e.g. no stack variables with automatic cleanup..).
From here I wonder if we should use gcc for more speedy compiles or if we should use more C++ features (I am not talking STL, operator overloading)?
Any opinions?
holger
PS: I think we should find a more nice solution to extern "C".. I spent various minutes trying to figure out which parts of the pcu have C linkage and which C++.. For things from libosmocore it is obvious.. but then we have the vty_info...
-- - Holger Freyther <hfreyther@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru