|
![](/i/fill.gif) |
Am 13.01.2014 11:19, schrieb andrel:
> On 13-1-2014 0:56, clipka wrote:
>> Am 12.01.2014 22:21, schrieb andrel:
>>
>
>> As for a function's name, I find it very important that it denotes not
>> /how/ the function does something, nor just /what/ it does, but also
>> with what /intention/.
>>
> True, but this is a general case where the point is that there are still
> several ways to do things. More specific names are needed lower in the
> tree.
> In this case I would go for something like:
>
> ECG=ComputeECGfromTiming(Timing,VolumeConductionModel,ElectricalModel,
> Parameters);
>
> or simply
>
> ECG=ComputeECGfromTiming(Timing,ForwardModel);
Sounds like a very good choice to me.
Post a reply to this message
|
![](/i/fill.gif) |