spend time to properly separate handover 2?

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Pau Espin Pedrol pespin at sysmocom.de
Mon Feb 12 18:34:14 UTC 2018


Hi Neels,

As somebody which may have to dig into that code at some point in time 
in the future, I'd back the option of having an entire set of parameters 
separated for each algorithm, even if some of them are repeated. If some 
stuff is repeated, let's try to abstract it and use some helper 
functions + structs, API, whatever to help reduce duplicated code.
The reasoning behind it: if I'm interested in algorithm 1, I don't need 
to know related details or care about reading stuff from algorithms 
2..N, I just need to know the API and use or extend it if needed.

-- 
- Pau Espin Pedrol <pespin at sysmocom.de>         http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte



More information about the OpenBSC mailing list