From laforge at gnumonks.org  Wed Aug 26 11:34:14 2015
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 26 Aug 2015 13:34:14 +0200
Subject: Mixed C and Python Code
In-Reply-To: <5538A494.8020400@morphism.de>
References: <5538A494.8020400@morphism.de>
Message-ID: <20150826113414.GU1065@nataraja>

Hi Martin,

the response is really late, but as nobody responded, it might be better
to have a late response, than none:

On Thu, Apr 23, 2015 at 09:51:48AM +0200, martin wrote:
> i want to ask why there is a mix of python and c code with lots of pipes
> in between.
> 
> It is a design decision? Or was it some kind of easyer?

The goal of the project was "let's try to have a decoder as
comprehensive as possible with as little time investment as possible".
The people involved in the various Osmocom projects are actually very
few, and available free/spare time is always at a premium.

So the python demodulator code was found/inheritet from the APCO25
project and just taken as-is.  The C code for the PHY and lower MAC was
written from scratch based on the specs and some textbooks.

After all, this is a FOSS project and it lives off contributions.  So if
somebody wants to streamline things more, and have an actual
architecture rather than a kludge of several independent parts, by all
means go ahead and implement it.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)